How sequencing works
Camera PULs with "PUL" user access accounts are able to send an xml file from the client to the server that contains high level pointing information such as coordinates, subframing, filters, bpp, etc. The server, which is behind a firewall, transforms this information into a sequence of capture_image commands. A PUL with an authorized account on the server can then scp the sequences from the server up to their working directory on fltops.
These sequences are copied into a "Viewpoint" sub-directory, and the files have a "-Viewpoint" filename tag, so that the PUL must open them up in RSVP Rose, inspect them, make changes, and then "save as" the sequence without the "-Viewpoint" tag to their working directory. So the final sequences which are delivered are always written by RSVP Rose (not Viewpoint), and only after the PUL has visually reviewed and possibly edited the commands. They are also then flight rule checked as usual.
This sequence writing process has been been a standard procedure for Pancam PULs with another piece of software, Panseq, since early 2004.
These sequences are copied into a "Viewpoint" sub-directory, and the files have a "-Viewpoint" filename tag, so that the PUL must open them up in RSVP Rose, inspect them, make changes, and then "save as" the sequence without the "-Viewpoint" tag to their working directory. So the final sequences which are delivered are always written by RSVP Rose (not Viewpoint), and only after the PUL has visually reviewed and possibly edited the commands. They are also then flight rule checked as usual.
This sequence writing process has been been a standard procedure for Pancam PULs with another piece of software, Panseq, since early 2004.