Trying to get a better idea of how some of the file types are used.
Can I simply edit the .variables file and have the variables update within the system when it runs?
For example - say I’m creating a script to add to an existing program, which will require adding a number of variables.
Rather than have to enter these variables while the robot is sitting there not being used, can I do this offline by adding these variables to a copy of the .variables file, then save this file back onto the robot (or a renamed version plus a renamed copy of the installation file)?
I’m not sure if the system actually uses that variables file or just pushes it out for reference like the program.txt file that’s created whenever a .urp is saved.
We don’t have the simulator set up anywhere, so when doing anything other than writing scripts, we’re locked into having the robot available, not running parts.
Similarly, on a brand new setup, it seems like we could create most of the variables up front this way.
It reads from it, so yeah I think you should be able to just edit it and resave. The simulator is free and easy to setup though, so I would definitely look into using it. Can be handy for offline programming the shell of your program.
Resurrecting this old thread, as things seem to have changed . . . . .
I actually came up with a real reason to want to edit this file – create several arrays with a number of elements using copy & paste-- and went to pull up the default.variables file.
However, it appears that in the newer versions of Polyscope that file format has changed from a basic text file to something unreadable.
Any of our v5.12 machines have readable files, but 5.13 and above show gibberish.
I could do this in a script, but I really want these to be installation variables (arrays of point features), which generally would be constant, but could be updated individually when necessary using a simple program to edit a specified array member.
Basically, I want to consolidate a couple hundred point features into 4 arrays of 10 - 16 poses and some offsets from those.
Not a huge deal to manually type in the basic array structure, but was thinking it would be neat to be able to minimize the typing.
In either case, they’ll all go in as zeros and I’ll teach/offset the points within a program.