Bug #176

Workshop Issue: spiceinit

Added by Tammy Becker about 7 years ago. Updated 10 months ago.

Target version:
Software Version:
Test Reviewer:


Please add the progess "%" or some activity indicator. Missions such as Cassini take quite awhile to load the kernels, the indication that it's working hard for the user is helpful.


#1 Updated by Stuart Sides over 6 years ago

Changes were made to the camera to allow it to find the correct kernels much faster. It should now be just a couple of seconds instead of many tens of seconds. If it is now fast enough I would like to consider closing this issue. If it is not, we can continue to looking at adding a progress. Please re-open, close, or stop by for additional details.

#2 Updated by Tammy Becker over 6 years ago

I have tested spiceinit under isis3.3.1 [2011Dec07].
The resulting 'connect and cpu time' are as follows:
ConnectTime = 00:00:07.0
CpuTime = 00:00:05.9

As compared to /usgs/pkgs/isis3nightly2010-12-01/isis/bin
ConnectTime = 00:00:12.0
CpuTime = 00:00:11.3

Obviously some time improvement.

Please note that the original request was still not addressed (though the speed improvement is obviously important), spiceinit still does not report a progress "%" or some activity indicator. This feedback to the user is helpful and should be consistent with the many other Isis apps that do (a good standard).

This issue needs to be reopened please.

Thank you

#3 Updated by Stuart Sides over 6 years ago

We will look into how this might be accomplished. At this time it may be reasonable to add a "WORKING" indicator, so the user knows something is happening (clock or hourglass)

Adding a % progress will have to be investigated. There are no nice indicators of how much work needs to be done for SPICE loading as there are for cubes (e.g., number of lines)

#4 Updated by Tammy Becker over 6 years ago

The agreed resolution of this issue is rather than the %, display some feedback to the user (even if it's printing to the screen the kernel that just was loaded), etc.

#5 Updated by Stuart Sides almost 6 years ago

This issue was discussed and a resolution agreed upon (see notes), but no programming was done. Issue unassigned.

#7 Updated by Anonymous about 5 years ago

  • Target version deleted (150)

#8 Updated by Stuart Sides about 4 years ago

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

#10 Updated by Stuart Sides over 3 years ago

  • Target version changed from 3.4.7 (2014-08-27 Aug) to 3.4.10 (FY15 R3 2015-07-23 Jul)

#12 Updated by Stuart Sides 10 months ago

  • Target version deleted (3.4.10 (FY15 R3 2015-07-23 Jul))

Also available in: Atom PDF