ScottThompson < Main

Tags: view all tags
   * Name: Scott Thompson
   * Login Name: scottt
   * Email: scottt@interchange.ubc.ca
   * Phone: 
   * Department: 
   * Comment: 

__My Links__
   * %TWIKIWEB%.WelcomeGuest to learn TWiki
   * Sandbox.WebHome web to try out TWiki
   * Sandbox.%TOPIC%Sandbox just for me

__Personal Preferences (details in %TWIKIWEB%.TWikiVariables)__


___Meeting Minutes___

__June 17, 2007 - Getting started (Scott, Rachel)__
* scope of project
* submit user account from for eb.cs.ubc.ca
* setup db lab access (ICICS X415)
* setup meeting with jiemin, others

__June 17, 2007 - Intro & current status(Scott, Jiemin)__
* Revit:
** Currently export to ODBC for main data source
** no cartesian co-ordinates for entities, (aka location information)
** Other Possible sources:
*** DWF (there is an api: DWF Toolkit, presently unexplored)
*** gbXML (this apparently only provides a partial export, and does not export all entities; for example, it might export walls, but not cielings)
*** "Embrace, Extend & Extinguish"
*** DWG - no location info (not examined in-depth; how is DWG diff from DWF?)
** Final format for data source: we won't have single format that combines all data. info will be provided on a query basis from multiple formats.
* Some discussion on procedures for using software.

Comments:
* AutoDesk has been known to follow microsoft's business approach, to standards (see:  "Embrace, Extend & Extinguish"). It's possible that autodesk has made a business decision to intentionally omit key (location) information in the data export in order to cripple a potentially threatening format.

__June 25, 2007 (Scott, Rachel, Brandon, Madnav, Jiemin, Sheryl)__

Approaches:
* Ji - Given design, how do we query the data?
* Ma - Given design, consider actions - identify what info we need.
* Ma - need prototyping info, etc

Slides:
* formalize conditions for design model
* "object based feature model" OBFM
* Sh: IFC is a feture model
* Ra: db people talk about "schemas"
* objects & implicit design considerations (id beams and wall intersections)
* how to populate 3D model
* query 3D model
* research framework (picture: domain knowledge -> generic feature templates -> instaniated models <-> query <-> 3D product model -> (feedback to generic feature template)
* Q: what level of detail is in the templates?
* Examples & Query Types
** alignment of supporting columns
** Ra: where to we define what it means to be aligned? A: generic feature template
** Sh: questions are pre-selected (aka pre-defined)
*** eg. are 2 components similar? what is the clear-span size? what is column spacing? are there patterns?
** Sh: terms like "moderate variation" need to be explicit
** eg. groupings of similar components
** eg. contractor reasoning about what is relevant
** eg. wall penetration - what? where? how many? properties of walls/ducts?
* IFC relations
** Parent-class relationships, etc
** attributes of components, pair, etc
* Penetration of walls is implicit
** Q: how to find implicit relationships?
* sh: IFS is _the_ industry standard
** rich on design, good architecturally
** undeveloped in building systems
** Q: product support?
** different models?
* Ma: what db structure do products (revit) use?
* Sh: need to document what info available from where
* Ra: the _research_ is in the methodology used to create the model
* Sh: archiCAD has better IFC integration
* Q: what is the market share of various CAD apps
* sh: there is a paper on Revit export/re-import, and how it is lossy

Next meeting: 2 weeks later, july 10. 3:00

Action Items:
* Ma: put slides on wiki
* Ji, Sc: location data extraction
* Ji: document the export sources and what info is exported
* Ma: document data required for query
* Ji: Share CAD models

Next steps:
a) simple queries
b) advanced, composidte, 3D queries
c) "derived" information
Raw edit | More topic actions
Topic revision: r2 - 2007-07-07 - ScottThompson