Understanding Seed File

Hi Jaimin,

You can use your MicroStation seed file to create new GC design file for sure.

In OBD , a more reliable strategy would be to create a new file using the seed file of the active WorkSet and then acquiring the GCT file through the script Editor. That way, the file’s working units set up will be fully aligned with the current WorkSet’s standards.

Whenever the user opens a GCT file, GC reads those measurement units, and applies them to the active master DGN file.

Here are few scenarios :

1. The user opens a GCT file, which, in turn, opens the seed DGN file. The units that are stored in the seed DGN file are irrelevant. Those units are overwritten, immediately, by the units stored in the GCT file.
2. During the session, the user wishes to change the units, so they do so via the standard mechanism (File -> Settings -> File -> Design File Settings).
3. Later, when user is finished working, they save the GCT file, At that point, the newly-changed units are written into the GCT file

4. Later still, the user re-opens the same GCT file, which presumably has the updated units .

   Here are the few examples how the units are saved in GCT file , the 1st example is showing English units and resolution.

   environment
   {
       GCVersion                 = '10.07.00.90';
       MSVersion                 = '10.14.00.101';
       MSProject                 = '';
       MSDesignFile              = 'D:TEST-GC-UNITS.dgn';
       MSMasterUnit              = {Meter, '''', English, 3048.0, 10000.0};
       MSSubUnit                 = {Meter, '"', English, 254.0, 10000.0};
       MSStorageUnit             = {Meter, '', English, 3048.0, 10000.0};
       MSUorsPerStorageUnit      = 304800.0;
   }

   Here is the another example where it is showing changes in Unit system by user which getting saved as metric units.

   environment
   {
       GCVersion                 = '10.07.00.90';
       MSVersion                 = '10.14.00.101';
       MSProject                 = '';
       MSDesignFile              = 'D:TEST-GC-UNITS.dgn';
       MSMasterUnit              = {Meter, 'm', Metric, 1.0, 1.0};
       MSSubUnit                 = {Meter, 'mm', Metric, 1.0, 1000.0};
       MSStorageUnit             = {Meter, '', Metric, 1.0, 1.0};
       MSUorsPerStorageUnit      = 25400.0;
   }

HTH,

Rg,

Sandeep

Hi Sundeep & Stuart,

Could a primary node (like baseCS) not be a useful place to explicitly set/define Units that the script uses? I appreciate the resolution of a file is stored in the DGN/Seed and should not be changed, but the choice of working units tends to be quite a personal thing. some like m, some like mm..
An option to automatically run through the nodes to reset the "apparent" unit in each one would be quite useful. In much the same way that you can retroactively store the position of nodes after they have been rearranged.

I suppose its hard to tell what is a unit value, vs just any old double, but maybe adding the unit abbreviation to the number is an option...

Regards

Robert

Hi Sundeep & Stuart,

Could a primary node (like baseCS) not be a useful place to explicitly set/define Units that the script uses? I appreciate the resolution of a file is stored in the DGN/Seed and should not be changed, but the choice of working units tends to be quite a personal thing. some like m, some like mm..
An option to automatically run through the nodes to reset the "apparent" unit in each one would be quite useful. In much the same way that you can retroactively store the position of nodes after they have been rearranged.

I suppose its hard to tell what is a unit value, vs just any old double, but maybe adding the unit abbreviation to the number is an option...

Regards

Robert

Hi Rob

I certainly have had in recent times a need to move a script from millimetres to metres and vice versa so I can see the value. It was a bit of an effort running through the script and multiplying or dividing values by 1000 to make that change. Any chance you could formalise that request via a ticket so it hits the system attached to your name?

As for the node, as you mention the unit is defined in the DGN and GC drives the values of things - distances etc, so it may need some thought related to the request on how that could be done. 

Stuart

No Problem, I'll generate the ticket, I just want to make sure I wasn't missing trick...;-)

eg. I know that if I rewind a script, then change units and replay a script it uses the current Master Unit and effectively scales everything, obviously it doesn't change the numerical value in the script itself.

I wonder if rewriting the values is a sane idea, vs simply making an explicit statement in something like the baseCS to say what the values represent and then regardless of the the files Master Unit, the script simply multiplies those distance values to fit.

When working in VBA I often create a small function just to convert units in exactly this way so that whatever master unit the user happens to be working with, the VBA script only deals in a consistent base unit (eg metres). The script just need to know what that the stored unit is.

Rob

https://www.skillscourses.org/The-Truth-About-Being-a-Leader.html

When you start learning over the web you are not always sure with your decision. The Truth About Being a Leader Course is the best decision I have mad to learn over the web. It is undoubtedly the best course I have ever found over the web portal.