VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Usage of relative path for calling a realtime sequence file

Hello everybody,

 

I'm having troubles with the distributed development of tests with VeriStand. We share the same codebase on different machines via Git. As there's no control over the absolute path where someone checks out the repository, I would like to make the calls from a sequence file to a realtime sequence relative.

I tried putting the stimulus profile and the realtime sequence in the same directory and just specify the name of the RT sequence in the call step. Unfortunately, this results in:

 

"The top-level sequence file 'C:\WINDOWS\system32\sequence.nivsseq' could not be found.

 

Is there a way to use relative paths for this that actually works?

 

Best regards,

MaWei

0 Kudos
Message 1 of 1
(2,335 Views)