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?

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

0 jpatterson over 4 years ago

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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 jpatterson over 4 years ago

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?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data