hexagon logo
Register Sign in
  • State Not Answered
  • Replies 6 replies
  • Subscribers 11 subscribers
  • Views 37 views
  • Users 0 members are here
Options
Related

Use of SAVE & RELOAD

jpatterson
I have a large A/View model that always starts out with the same "short" dynamic event, and then gets sent to several other subsequent events. Looking at the SAVE & RELOAD commands, it seems I should be able to do something like the following two major tasks...
 
  • Configure the model as needed
  • Make my short run via an initial.acf in batch.
  • Issue "SAVE/SYSTEM, FILE=initial.sav" at the end of the initial.acf
 
This file is now sitting on my hard drive, then...
 
  • Create a desired_run.acf file
  • The first line should be "RELOAD/SYSTEM, FILE=initial.sav, OUTPUT_PREFIX=Test_out"
  • Solve in batch
  • Etc. with other desired runs
 
When I try this, I get the following error in the .msg file...
 
 command: ! Insert ACF commands here:
 command: 
 command: RELOAD/SYSTEM, FILE=initial.sav, OUTPUT_PREFIX=Test_out
 
---- START: WARNING ----
Problem reading FILE=initial.sav referenced in RELOAD/SYSTEM command.
Check spelling and/or existence of file. File names are case sensitive.
Command aborted.
---- END: WARNING ---
 
Is my interpretation of how this should work correct? Any thoughts?
  • 0
    In the reload-acf you still have to specify an adm-file at the top. After this you do the reload/system
     
    With the reload you will get the state of your saved model. Did you consider how you would modify this to get the model to do the desired event?
  • 0
    Hi Henrik,
     
    Thanks for the reply.
     
    Yes, there is a "file/model=desired_run" command at the beginning of the 2nd acf file. I'm creating the acf as a script in A/View first.
     
    I'm not sure I understand your second question/comment (which might be the problem!).
     
    My first event is a vehicle driving straight at a set speed. My subsequent event(s) would continue that scenario and then apply the brakes or turn or hit a bump. Am I imagining this process correctly?
  • 0
    I had to read up on this again from the Online Help to see if I remembered correctly, but unfortunately I did.
     
    The problem with the solver SAVE/SYSTEM and RELOAD/SYSTEM is that when you use these, you really do save and reload the whole system including everything. This means that no matter what adm-file you have in your "desired_run", when you use the RELOAD/SYSTEM, you reload the full model of the "initial" run. Hence any breaking or other stuff you would have added is not preserved.
     
    So to use this, you will actually have to do what is suggested in the Adams Solver Online Help for the SAVE and RELOAD commands - do the modifications to the model from the acf-file. This is possible, but can be quite cumbersome.
  • 0
    I don't think the adm is an issue for what I have in mind...
     
    I will not need to modify anything (activate/deactivate) for these runs. I'm just trying to do the initial part of the run once because the model takes a long time to find static and then still settle out some transients. My events (Braking, turning, etc.) would be timed out such that they would start after this initial run ends. Something like...
     
    Static & initial dynamic is from t=0s-2s (This part takes 30 minutes to solve)
    Reload from that spot for an event that starts at t=3s and runs until t=6s (This part takes 3 minutes to solve)
  • 0
    This is how it works:
    Run a model driven by a motion.
    Initial setup: Motion function = 720d * step(time,0,0,1,1)
    Do the initial run:
    file/model=initial
    sim/dyn,end=1,dtout=0.01
    save/system,file=initial.sav
    stop
     
    Change the motion function: 720d * step(time,0,0,1,1) + 90d * step(time,2,0,4,1)
    Do the second run:
    file/model=second
    reload/system,file=initial.sav,output=second
    sim/dyn,end=5,dtout=0.01
    stop
     
    In the result from the second run, the motion will be running a constant 720d, and will not be increased by the 90d between 2 to 4 seconds.
     
    So in order to run anything that is different from the original model, you have to do the changes to the model from the acf-file after doing the reload/system
  • 0
    Would this sequence work...???
     
    I want the Brakes to come on at t=2s
    Initial setup: Step function = step(time,2,0,5,1)
     
    Do the initial run (Takes 30 minutes):
    file/model=initial
    sim/dyn,end=1,dtout=0.01
    save/system,file=initial.sav
    stop
     
    Do the second run (Takes 3 minutes):
    file/model=second
    reload/system,file=initial.sav,output=second
    sim/dyn,end=5,dtout=0.01
    stop
© 2025 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement