Object GUID and attributes

VisualARQ
1

Hi all,

I am new to Visual ARQ and I have a question related to the object GUID.

I used VisualARQ to add parameters to an object. When I need to modify the parameters, I have to bake the object again. So, Rhino will create new object with new GUID. This causes trouble for the estimation software to recalculate since it recognizes the object as a new one.

Is there any way to update the parameters of an object while can keep its original GUID?
If it can be done with GHpython it would be great.

Your help is much appreciated.

Best regards

Tran Dang

element parameter.PNG
element parameter.PNG1633×612 87.5 KB

2

Hi @archdang you can use the Update Property component instead, which preserves the object ID.

UpdateProperty
UpdateProperty1321×530 299 KB

3

Dear Francesc,
Thank you so much for your help, the problem is solved. I wonder when could we access the Visual ARQ api in GHpython.
Cheers
Tran

4

@archdang you are welcome! There is already an API available for VisualARQ (although no documentation yet). In this thread you can find some details: VisualARQ API - #2 by enric

And here some examples: Is there an API or SDK for VisualARQ? - VisualARQ

We are adding more functions for the VA API on demand. So don’t hesitate to let us know what you are needing to do or what you are missing.

5

Thanks Francesc,
It is great to hear that the API is there I think it will be very helpful when the document is in place.

Also, I found a couple things related to the IFC export process that we need help please .
In Rhino, it is great that we can keep update attributes while keep GUID of object.
However, when I export to IFC files, the 3 values: IFCPROJECT, IFCSITE, IFCRELCONTAINEDINSPATIALSTRUCTURE: are keep changing. Only IFCPROXY is remained.
Please find attached images for the comparison.

My question are:
1.Could we control the values of IFCPROJECT, IFCSITE, IFCRELCONTAINEDINSPATIALSTRUCTURE?
2. What is the relationship between Rhino GUID and the IFC Guid of geometry when exported? is there any way to control them is your exporting process?

These values has affected our estimating process using a third party software since it based on GUID for checking revision.
Thank you in advance and your help is much appreciated.

Best regards
Tran Dang

IFC_values declare
IFC_values declare1387×720 601 KB
IFC_values declare2
IFC_values declare21415×706 650 KB

6

Hi @archdang,
The information about ifcProject and ifcSite can be assigned to the document through the Document User Text dialog, or through the command line (SetDocumentUserText command). These are the user text keys available:

  • IfcProject_Name
  • IfcProject_Description
  • IfcProject_LongName
  • IfcProject_Phase
  • IfcSite_Name
  • IfcSite_Description
  • IfcSite_LongName

As regards objects GUID, VisualARQ always keeps the objects’ GUID when it exports them to IFC. But when the same model it’s imported, a new GUID is assigned to each object, and this new one will be exported to IFC the next time you export the model.

However, in other entities GUID (such as IfcSite, IfcProject, or relations…) a random GUID is generated each time the file is exported to IFC). We could make the GUID in these entities was preserved (when exporting the model to IFC), if you wish.

7

Dear Francesc,
Thank you for your response.
In our case, we need to preserve as much as possible all the GUIDs of those entities for revision purposes.
Could you please help us with that.
Thank you in advance
Best regards
Tran

8

All right, we will try to keep GUID’s on IfcSite, IfcProject, etc… in future versions.

9

Dear Francesc,
It should be great, we appreciate your supports. We are looking forward to trying the new version. A little hint about the release time frame should be great for us if you do not mind.
Thank you in advance,
Best regards
Tran Dang

10

Hi @archdang, it’s still soon to do a fair estimation when version 3 will be released. The earliest might be in 2022. Hopefully, we will release a WIP version in a few weeks that will be available for VisualARQ users.