完善主體資料,免費贈送VIP會員!
      * 主體類型
      * 企業名稱
      * 信用代碼
      * 所在行業
      * 企業規模
      * 所在職位
      * 姓名
      * 所在行業
      * 學歷
      * 工作性質
      請先選擇行業
      您還可以選擇以下福利:
      行業福利,領完即止!

      下載app免費領取會員

      NULL

      ad.jpg

      BIM手冊中文版(譯文):第二章_2.3.4節-可伸縮性

      發布于:2018-06-29 21:44:54

      BIM譯站

      更多

      譯文:


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

      參數化建模整合了設計規則,即將某一構件的形狀和參數關聯到另一個構件的形狀和參數中。這些規則形成了關系層次:構件內參數化關系、構件間參數化關系,根據另一個構件的變化調整某一構件的形狀,控制軸網和控制曲面之間的層次關系決定了形狀的參數和一組相關聯構件的放置。雖然構件內和構件間的參數化關系是構件的局部更新,但是這種層次規則的擴散可更新整個模型。局部參數化規則擴散只在模型上產生合理要求,然而某些系統架構卻限制了管理這種大批量層次規則傳播的能力。同樣,把項目分成若干部分來開展的同時仍然管理大批量層次關系是很困難的。

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

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

      內存和處理方面的問題,將會隨著計算機運行越來越快而自然減少。64位處理器和操作系統也提供了重要的幫助。但與此同時,也會有更加細化的建筑模型和更大規模參數化組方面的需求。可伸縮性方面的問題還會繼續存在一段時間。


      原文:


      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.


      版權說明:本文來源BIM譯站微信公眾號,轉載已取得授權

      公眾號名稱:BIM譯站

      公眾號賬戶:BIM2018130

      rr.jpg

      本文版權歸腿腿教學網及原創作者所有,未經授權,謝絕轉載。

      未標題-1.jpg

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

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

      主站蜘蛛池模板: 国产一区三区二区中文在线| 久久久精品人妻一区二区三区四 | 国产午夜精品免费一区二区三区| 日韩精品一区二区三区四区| 国产日韩精品一区二区三区| 伊人久久精品无码av一区| 国产成人av一区二区三区在线 | 国产中文字幕一区| tom影院亚洲国产一区二区 | 亚洲av不卡一区二区三区| 一区二区高清在线| 午夜视频在线观看一区| 在线精品一区二区三区电影| 中文字幕乱码亚洲精品一区| 制服丝袜一区在线| 国产精品一区二区不卡| 国产精品一区二区不卡| 精品无人区一区二区三区| 无码人妻精品一区二区在线视频| 色妞AV永久一区二区国产AV| 精品视频在线观看你懂的一区| 国产一区二区三区不卡在线看| 亚洲av综合av一区二区三区| 亚洲一区二区三区成人网站| 精品一区二区三区在线播放视频 | 亚洲美女视频一区二区三区| 人妻体内射精一区二区三区| 一区二区三区国产精品| 在线观看亚洲一区二区| 精品无码人妻一区二区三区| 亚洲一区中文字幕| 综合无码一区二区三区四区五区| 亚洲一区在线观看视频| 日本一区二三区好的精华液 | 国产在线视频一区二区三区98| 国产品无码一区二区三区在线蜜桃| 夜夜添无码试看一区二区三区| 久久99精品波多结衣一区| 亚洲福利一区二区三区| 日本精品一区二区三区视频| av在线亚洲欧洲日产一区二区|