譯文：

很多用戶遇到的問題是可伸縮性。當(dāng)項(xiàng)目模型在實(shí)際使用的時(shí)候變得非常大時(shí)，就會遇到可伸縮性的問題。當(dāng)運(yùn)行變得遲鈍，哪怕很小規(guī)模的運(yùn)行也會非常費(fèi)力。建筑模型用掉了電腦很多內(nèi)存空間。大型建筑會包含上百萬個(gè)不同形狀的構(gòu)件。可伸縮性同時(shí)受建模規(guī)模（比如樓層面積）和模型中的詳細(xì)程度影響。即使在一個(gè)簡單的建筑中，如果對每個(gè)釘子和螺絲都建模，也會出現(xiàn)可伸縮性問題。

參數(shù)化建模整合了設(shè)計(jì)規(guī)則，即將某一構(gòu)件的形狀和參數(shù)關(guān)聯(lián)到另一個(gè)構(gòu)件的形狀和參數(shù)中。這些規(guī)則形成了關(guān)系層次：構(gòu)件內(nèi)參數(shù)化關(guān)系、構(gòu)件間參數(shù)化關(guān)系，根據(jù)另一個(gè)構(gòu)件的變化調(diào)整某一構(gòu)件的形狀，控制軸網(wǎng)和控制曲面之間的層次關(guān)系決定了形狀的參數(shù)和一組相關(guān)聯(lián)構(gòu)件的放置。雖然構(gòu)件內(nèi)和構(gòu)件間的參數(shù)化關(guān)系是構(gòu)件的局部更新，但是這種層次規(guī)則的擴(kuò)散可更新整個(gè)模型。局部參數(shù)化規(guī)則擴(kuò)散只在模型上產(chǎn)生合理要求，然而某些系統(tǒng)架構(gòu)卻限制了管理這種大批量層次規(guī)則傳播的能力。同樣，把項(xiàng)目分成若干部分來開展的同時(shí)仍然管理大批量層次關(guān)系是很困難的。

問題就在于內(nèi)存大小。所有構(gòu)件形狀方面的運(yùn)行都必須占用內(nèi)存。管理參數(shù)化更新的一個(gè)簡單方法就是把項(xiàng)目存儲在內(nèi)存中。如此便對可伸縮性產(chǎn)生了挑戰(zhàn)，并且對可進(jìn)行有效編輯的項(xiàng)目模塊之規(guī)模做出了實(shí)際限制。然而，如果規(guī)則可在文件之間進(jìn)行傳播，即在某一文件中更新某一構(gòu)件能致使其它文件自動更新，那么對項(xiàng)目規(guī)模大小的限制便會消失。僅有少量專門為建筑開發(fā)的應(yīng)用程序有管理參數(shù)化變更在多文件之間傳播的手段。我們把必須將所有更新的構(gòu)件同時(shí)存儲在內(nèi)存中的系統(tǒng)稱為“基于內(nèi)存”。當(dāng)模型大到難以存儲在內(nèi)存中時(shí)，就會出現(xiàn)虛擬內(nèi)存交換，這會造成大量等待時(shí)間。其它系統(tǒng)有在文件之間傳播關(guān)系和更新的手段，并且能在編輯操作期間打開、更新以及關(guān)閉多個(gè)文件。我們稱這些系統(tǒng)為“基于文件”型系統(tǒng)。基于文件型系統(tǒng)運(yùn)行小型項(xiàng)目一般會有些慢，但是隨著項(xiàng)目文件變大其運(yùn)行速度降低的也慢。

用戶將項(xiàng)目分成若干模塊已經(jīng)是一種久經(jīng)考驗(yàn)的共享工作之手段并且限制了自動更新的規(guī)模。參照文件往往也被用于限制可編輯的模塊。如果項(xiàng)目中的層次關(guān)系不會造成全局項(xiàng)目變更，這些操作是相當(dāng)有效的。有些BIM工具加強(qiáng)了這些限制。

內(nèi)存和處理方面的問題，將會隨著計(jì)算機(jī)運(yùn)行越來越快而自然減少。64位處理器和操作系統(tǒng)也提供了重要的幫助。但與此同時(shí)，也會有更加細(xì)化的建筑模型和更大規(guī)模參數(shù)化組方面的需求。可伸縮性方面的問題還會繼續(xù)存在一段時(shí)間。

原文：

A problem that many users encounter is scalability. Problems in scaling are encountered when a project model gets too large for practical use. Operations become sluggish, so that even simple operations are laborious. Building models take a lot of computer memory space. Large buildings can contain millions of objects, each with a different shape. Scalability is affected by both the size  of the building, say in floor area, and also by the level of detail in the model. Even a simple building can encounter scalability problems if every nail and screw is modeled.

Parametric modeling incorporates design rules that relate geometry or other parameters of one object with those of other objects. These come in a hierarchy of relations: within object parametric relations, peer object relations, adjusting one object’s shape in response to the change of another object, and hierarchical relations between control grids and surfaces that determine the parameters of shape and placement of a set of associated objects. While within object and peer object relations update locally, hierarchical rule propagation may generate updates to the whole building. Local parametric rule propagation makes only reasonable demands on models, while some system architec- tures limit the ability to manage propagation of large sets of hierarchical rules.Also, it is hard to partition a project into parts for separate development and still manage a large set of hierarchical rules.

The issue is memory size; all operations on object shapes must take place in memory. The simple solution to manage parametric updates is to carry the project in memory.  This challenges scalability and places practical limits on  the size of a project module that can be effectively edited. However, if rules can be propagated across files, where updating an object in one file can lead to automatic updates propagated to other files, the size limitation of a project disap- pears. Only a few BIM design applications developed especially for architecture have the means for managing parametric change propagation across multiple files. We call systems that must carry all updated objects in memory simultaneously memory-based. When the model gets too large to be held in memory, virtual memory-swapping occurs, which can result in significant waiting time. Other systems have methods of propagating relations and updates across files and can open, update, and then close multiple files during an edit operation. These are called file-based systems. File-based systems are generally a bit slower for small projects but their speed decreases very slowly as project size grows.

User segmentation of projects into modules has been a time-tested way  of sharing work and limiting the scale of automatic updates. Reference files   are often used to also limit what can be edited. These work well if hierarchical relations in a project don’t lead to global project changes. Some BIM tools impose these limitations.

Memory and processing issues will naturally decrease as computers get faster. Sixty-four-bit processors and operating systems also provide significant help. There will be the parallel desire, however, for more detailed building models and larger sets of parametric rules. Issues of scalability will be with us for some time.

版權(quán)說明：本文來源BIM譯站微信公眾號，轉(zhuǎn)載已取得授權(quán)

公眾號名稱：BIM譯站

公眾號賬戶：BIM2018130

本文版權(quán)歸腿腿教學(xué)網(wǎng)及原創(chuàng)作者所有，未經(jīng)授權(quán)，謝絕轉(zhuǎn)載。

上一篇：Revit鋼筋算量的探索和晨曦BIM插件

下一篇：公眾號：【BIM譯站】BIM英文書籍連載說明

猜你喜歡

什么是存水彎？

分流式排水與合流式排水有什么區(qū)別？

根據(jù)在結(jié)構(gòu)中的作用，鋼筋有哪些分類？

如何自學(xué)建筑設(shè)計(jì)之大頭幫主（三）學(xué)會如何表達(dá)

這是一篇教你看懂梁平法的文章（上）

C4D教程系列第四期—C4D多窗口創(chuàng)建合并篇

最新課程

隧道工程識圖（盾構(gòu)法）

工程基礎(chǔ)

46773人已學(xué)

隧道工程基本內(nèi)容

工程基礎(chǔ)

40294人已學(xué)

隧道工程識圖（鉆爆法）

工程基礎(chǔ)

34196人已學(xué)

工程基礎(chǔ)：橋梁工程識圖

工程基礎(chǔ)

50951人已學(xué)

BIM必修課：電氣識圖

工程基礎(chǔ)

86314人已學(xué)

BIM必修課：暖通識圖

工程基礎(chǔ)

101996人已學(xué)

推薦專題

Revit下載全版本2014~2025專輯

Revit離線族庫、樣板、族樣板專輯

BIM電腦配置專輯

全國BIM等級考試相關(guān)內(nèi)容專題

全國BIM標(biāo)準(zhǔn)合集

Revit常見安裝問題專輯

1+X歷年真題合輯

Revit基礎(chǔ)工具詳解專輯

廣聯(lián)達(dá)軟件下載專題-MagiCAD下載,施工建模,模板腳手架,BIM5D

bim模型手機(jī)查看軟件專題

bim軟件_bim軟件有哪些_bim軟件介紹_bim軟件多少錢一套

Revit2024專題-Revit2024下載,Revit2024教程,Revit2024新功能

成塔混動設(shè)計(jì)

Revit2025專題

CATIA軟件專題

SketchUp軟件專題

V-Ray軟件專題

Enscape軟件專題

AutoCAD軟件專題