SACS - Additional Model Information in the 2nd input file

Dear Bentley,

I have question about the model information i.e member group, member section etc.

Can we separate those information i.e. not contain the same sacs inputfile similar to seainp?

For Seastate information, we can provide additional seastate information in the seainp and put File B to merge both information provided in the sacinp and seainp.

Can we do the same for model information i.e member group, member section?

Fex,

In the picture, the left hand side is the main model i.e. sacinp contains most of the model information.  The right hand side is the additional model information which we need to incorporate in the model before start to execute the analysis.

I noticed that seainp file has option to add GRUP and MEMBER command, however, it will not be added to the main model input file. It will override all information in the main input file which is not my intention.

I would like all information are merged before start to analyze the problem.

Can you help to suggest about this?

Regards,

Kasiphon

Parents
  • There is no support for partial model files at this time, although we are discussing various ways to add support for something like this in the future.

    The best workflow I've found for using a partial model file is to open the base model file in Precede, import the partial model file, and then save the resulting file as your combined model. Obviously this isn't very efficient if you are wanting to keep these file separate and programmatically combine the files at analysis time. I am assuming that this is intended to represent a temporary structure during a pre-service condition like lift or loadout.

    One thing that you might want to consider is our new SACS API which is available as a tech preview in SACS 15.0 (with a big update coming in SACS 15.1). The SACS API allows you to open a model and programmatically add, modify, or delete SACS model elements and save that to a separate model file. You can even use the SACS analysis engine to run the analysis from the same script. So the proposed workflow would look like:

    1. Modify base SACS model file (sacinp.xxx)
    2. Run Python SACS API Script
      1. Add additional joint data
      2. Add additional group data
      3. Add additional member data
      4. Save as preservice SACS model file (sacinp.lift)
      5. Perform lift analysis with SACS Analysis Engine

    The only limitation here is that you will need to be careful about how you existing reference joints in the base model. If you modify those joints, then you will need to update your script accordingly.

    The SACS API documentation is available under [SACS]\Docs\HTML\index.html.

    An example of python script using the SACS API with the SACS Analysis Engine is available in SACS Executive under Projects > Demo Projects > Demo 14 - Batch Processing.

    Regards,

    Geoff

    Answer Verified By: Kasiphon Kurojjanawong 

Reply
  • There is no support for partial model files at this time, although we are discussing various ways to add support for something like this in the future.

    The best workflow I've found for using a partial model file is to open the base model file in Precede, import the partial model file, and then save the resulting file as your combined model. Obviously this isn't very efficient if you are wanting to keep these file separate and programmatically combine the files at analysis time. I am assuming that this is intended to represent a temporary structure during a pre-service condition like lift or loadout.

    One thing that you might want to consider is our new SACS API which is available as a tech preview in SACS 15.0 (with a big update coming in SACS 15.1). The SACS API allows you to open a model and programmatically add, modify, or delete SACS model elements and save that to a separate model file. You can even use the SACS analysis engine to run the analysis from the same script. So the proposed workflow would look like:

    1. Modify base SACS model file (sacinp.xxx)
    2. Run Python SACS API Script
      1. Add additional joint data
      2. Add additional group data
      3. Add additional member data
      4. Save as preservice SACS model file (sacinp.lift)
      5. Perform lift analysis with SACS Analysis Engine

    The only limitation here is that you will need to be careful about how you existing reference joints in the base model. If you modify those joints, then you will need to update your script accordingly.

    The SACS API documentation is available under [SACS]\Docs\HTML\index.html.

    An example of python script using the SACS API with the SACS Analysis Engine is available in SACS Executive under Projects > Demo Projects > Demo 14 - Batch Processing.

    Regards,

    Geoff

    Answer Verified By: Kasiphon Kurojjanawong 

Children
No Data