hexagon logo

Use of SAVE & RELOAD

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?
Parents
  • 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)
Reply
  • 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)
Children
No Data