Feature #1237

New Tool: Update Serial Numbers in Existing Control Networks

Added by Lynn Weller over 5 years ago. Updated 7 months ago.

Target version:
Software Version:
Test Reviewer:


Although not frequent, on more than one occasion the serial number for images from active missions have changed over the course of the time. This is a problem when control networks have been built with images that have experience changes that affect the serial number. If the network isn't too big and if the number of images affected aren't many, the typical user is likely to convert the binary net to an ascii file and update it manually via their favorite editor or via an awk or perl script. But in the case of very large networks (say 37,000+ images and over 2 million measures), converting to ascii and modify via script or editor is prone to pilot error and is frankly cumbersome. We need a tool to take care of this issue that exists, albeit not on a daily basis.

Don't ask me who should pay for this....I have no clue. Any active mission that astro has built a control net for that has some sort of timing change after the fact may be affected. All I know is this is a tool we can use, hence the request.


#2 Updated by Anonymous almost 5 years ago

  • Target version deleted (150)

#3 Updated by Lynn Weller over 4 years ago

  • Priority changed from Normal to High

#4 Updated by Kristin Berry about 4 years ago

  • Target version set to 3.4.7 (2014-08-27 Aug)

#6 Updated by Stuart Sides almost 4 years ago

  • Target version changed from 3.4.7 (2014-08-27 Aug) to 159

#10 Updated by Stuart Sides over 3 years ago

  • Target version deleted (159)

#12 Updated by Stuart Sides about 1 year ago

  • Target version set to 3.5.1 (Sprint 1)

#13 Updated by Stuart Sides 11 months ago

  • Target version changed from 3.5.1 (Sprint 1) to 3.5.2 (2017-01-31 Jan)

#14 Updated by Stuart Sides 7 months ago

  • Target version deleted (3.5.2 (2017-01-31 Jan))

On hold until a good solution is found

Also available in: Atom PDF