Uploaded image for project: 'GMAT'
  1. GMAT
  2. GMT-4413

Adding Spacecraft to OrbitView (propagated by SPICE file) Crashes GMAT

    Details

      Description

      Download the script and SPK kernel
      Modify the script to point to where you put the SPK kernel
      Run the script
      Go to DefaultOrbitView and open dialog box
      In ViewObject box, Spacecraft list, add Spacecraft1 to Selected Spacecraft
      Click OK to close
      Run from Run button in toolbar.

      I see a crash at this point

      =========================

      Another Bug related to SPICE file found on 03/19/2014:

      GMAT build being used is March 12th and platform is Windows Enterprise 64 bit

      1. I have attached another GMAT OSIRIS script (OREx_CRASH.script). You will need to use attached spice file (Ast_EphermisFile.bsp) for this script. Please put Ast_EphermisFile.bsp in GMAT's spk folder (...data\planetary_ephem\spk).

      2. Now upload this script and hit save/sync/run this script as it is. Script will run just fine.

      3. Go to Resources tree. Now open ephemerisFile1 and change Stepsize to 86400, click OK and hit RUN in GUI mode. You will see an exception. Just hit OK on the exception.

      4. Now hit RUN in GUI mode again and you'll see a CRASH!

      Note This is related to SPICE because EphermerisFile2 generates SPICE ephemeris. If you delete EphemerisFile2 resource and follow steps 1 through 4, then you will ONLY see exception being thrown and no crash. So the crash is occurring when EphemerisFile2 resource is there.

        Gliffy Diagrams

          Attachments

          1. Ast_EphermisFile.bsp
            25 kB
          2. EphemerisFile1.bsp
            14 kB
          3. OREx_CRASH.script
            27 kB
          4. SPICETest.script
            9 kB

            Activity

            Hide
            gmat_wcs Wendy Shoan added a comment -

            It looks like there may be another issue with writing the output SPK file. When I ask CSPICE to give me LONG messages, it writes this to the error file, indicating to me that it couldn't even open the file (though the file does get created and exists in the output file):
            ================================================================================

            Toolkit version: N0064

            SPICE(FILEOPENFAIL) –

            Attempt to create new file, '../output/EphemerisFile22222222222.bsp' failed.
            IOSTAT was 128.

            A traceback follows. The name of the highest level module is first.
            spkopn_c --> SPKOPN --> DAFONW --> ZZDDHOPN

            ================================================================================

            ================================================================================

            Toolkit version: N0064

            SPICE(NOSEGMENTSFOUND) –

            No segments were found in the SPK file
            '../output/EphemerisFile22222222222.bsp'. There must be at least one segment in
            the file when this subroutine is called.

            A traceback follows. The name of the highest level module is first.
            spkcls_c --> SPKCLS

            ================================================================================

            Show
            gmat_wcs Wendy Shoan added a comment - It looks like there may be another issue with writing the output SPK file. When I ask CSPICE to give me LONG messages, it writes this to the error file, indicating to me that it couldn't even open the file (though the file does get created and exists in the output file): ================================================================================ Toolkit version: N0064 SPICE(FILEOPENFAIL) – Attempt to create new file, '../output/EphemerisFile22222222222.bsp' failed. IOSTAT was 128. A traceback follows. The name of the highest level module is first. spkopn_c --> SPKOPN --> DAFONW --> ZZDDHOPN ================================================================================ ================================================================================ Toolkit version: N0064 SPICE(NOSEGMENTSFOUND) – No segments were found in the SPK file '../output/EphemerisFile22222222222.bsp'. There must be at least one segment in the file when this subroutine is called. A traceback follows. The name of the highest level module is first. spkcls_c --> SPKCLS ================================================================================
            Hide
            rqureshi Rizwan Qureshi added a comment -

            Wendy: Just FYI. Since you're already working on spice related crash, I combined this new spice related crash with this ticket per Steve's recommendation.

            Show
            rqureshi Rizwan Qureshi added a comment - Wendy: Just FYI. Since you're already working on spice related crash, I combined this new spice related crash with this ticket per Steve's recommendation.
            Hide
            gmat_wcs Wendy Shoan added a comment -

            This should be fixed now, in the 25 March build.

            Show
            gmat_wcs Wendy Shoan added a comment - This should be fixed now, in the 25 March build.
            Hide
            rqureshi Rizwan Qureshi added a comment -

            The description had 2 different instances of crashes involving SPICE file. I have verified both bugs and now crashes do not occur any more. Verified the 2 bugs using 04/04/14 build.

            Show
            rqureshi Rizwan Qureshi added a comment - The description had 2 different instances of crashes involving SPICE file. I have verified both bugs and now crashes do not occur any more. Verified the 2 bugs using 04/04/14 build.
            Hide
            rqureshi Rizwan Qureshi added a comment -

            Closing this bug since verification is done.

            Show
            rqureshi Rizwan Qureshi added a comment - Closing this bug since verification is done.

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 hours
                  3h