Project SWA + Resolution Questions

Marc has added some interesting material on his blog on AecoSim settings.

We are working on a project with the following settings:

Resolution: 10000 per Meter

Solids Working Area: 429.496 Kilometers

0,0,0 is about 81 km away from the centre of the project.

Both seem to be well above the recomendations suggested in Marc's blog above:

Resolution: 10000 per MM

SWA 4.29km

Q1: Is the SWA is centred on the Design Cube? If so should we be moving the DC centre closer to the project footprint? Is this done by using "GO=" ?

Q2: Should we be changing the resolution/SWA mid stream? What happens if we need to reference some 'infrastructure-scale' models? Will referencing using Coincident World take care of this?

Parents
  • Unknown said:

    Q1: Is the SWA is centred on the Design Cube? If so should we be moving the DC centre closer to the project footprint? Is this done by using "GO=" ?

    The SWA is just a scale factor. Ideally you should model near 0,0,0 uors and use GO= to specify the real-world coordinate of 0,0,0...this will avoid potential problems with large floating point numbers.

    Unknown said:

    Q2: Should we be changing the resolution/SWA mid stream? What happens if we need to reference some 'infrastructure-scale' models? Will referencing using Coincident World take care of this?

    Changing the SWA of a model after smart solids have been created can be problematic. The difference in scale between the old and new SWA will be applied when doing things like a Boolean union between solids and could easily make the solid too small or too large for the new SWA. So it all depends on the element size and new SWA scale whether it will cause problems to change it.

    Coincident world references will align your model's global origins...true scale will account for unit differences between the models. The SWA doesn't come into play until you copy elements between models or try to perform solids operations between elements in the master file and reference. To minimize potential problems for things like merging references, it's best to use the same unit setup for all models in a project.

    HTH

    NOTE: Changing resolution does not change the SWA scale as it's a uor scale (which means a 1 km SWA isn't the same number of uors when you have different unit settings for your models)...changing resolution after the fact is also not recommended, true scale/coincident world attachments are the way to go.



  • Hi Brien,

    Thanks very much for the response:

    1. So, if the project footprint should be as close to 0,0,0, ours, then we should be using GO=0,0,0¦ours?

    2. In some of one of the posts, you mentioned smartsolids were not initially updated to have a 'floating' SWA origin. Can you confirm whether AecoSIm's Forms have been updated?

    3. I also seem to recall that there was a recommendation to remain within the 4.29m cube at a high resolution for DEM to work properly. Is this still the case? In which case, we have a problem with our current settings.

    4."Coincident world references will align your model's global origins...true scale will account for unit differences between the models."

    But if everyone is modeling at 0,0,0¦ours, then Train Station A can't Ref Train Station B with CW/True Scale.... right?

    What the heck happens when you activate a Ref...?

    5. "Changing the SWA of a model after smart solids have been created can be problematic. The difference in scale between the old and new SWA will be applied when doing things like a Boolean union between solids and could easily make the solid too small or too large for the new SWA. So it all depends on the element size and new SWA scale whether it will cause problems to change it."

    Surely, there should be a tool to recalibrate the solids to maintain their 'real world' dimensions when the user changes the SWA scaling? A 10m beam should stay 10m. The recalibrating tool would rejig whatever Parasolids looks at to maintain mathematical happiness?

    6. Will 64bits help? You don't see this kind of fiddling required of the poor user with most apps....?  Even CAD Admins have trouble getting their heads around this stuff.

  • Dom,

    Frm experience, AECOsim does not use a floating SWA. We've gone back to renaming the GO, for AECOsim projects.



Reply Children
No Data