Spice doesn't retain loaded data kernels

[bbercoviciUspace]

Hello everyone,

I've stumbled upon a Spice problem I had not encountered yet : although data kernels are available on my compute (de430.bsp to name one) are properly loaded (since the Reset() method of SpiceInterface proceeds without errors), it appears that Spice simply loses track of the loaded kernels when it is time for Update() to be called.

Here's the error I am getting upon running test_unitSpice.py . I'm 100% positive that this error is thrown when spkezr_c is called in SpiceInterface::pullSpiceData.

I've downloaded the data kernels directly from NAIF and still got the same error, so it doesn't seem to be a data corruption issue.

Not having the toolkit C sources prevents me from running gdb , so I'm at loss regarding what may be happening here.

Any advice?

================================================================================
 
Toolkit version: N0065
 
SPICE(NOLOADEDFILES) --
 
At least one SPK file needs to be loaded by SPKLEF before beginning a search.
 
A traceback follows.  The name of the highest level module is first.
spkezr_c --> SPKEZR --> SPKEZ --> SPKGEO --> SPKSFS
 
Oh, by the way:  The SPICELIB error handling actions are USER-TAILORABLE.  You
can choose whether the Toolkit aborts or continues when errors occur, which
error messages to output, and where to send the output.  Please read the ERROR
"Required Reading" file, or see the routines ERRACT, ERRDEV, and ERRPRT.
 
================================================================================

[bbercoviciUspace]

I was able to track the issue down to the corruption of de430.bsp that arose in the context of multiprocessed simulations (probably when the Reset() method of spiceInterface was called) . sha1sum de430.bsp returned a hash value that didn't match that of the kernel file freshly downloaded from Github.

This overall makes me very dubious about Spice and Basilisk's ability to conduct multi-processed simulations featuring spice interface modules in a sound and sustainable manner. @patkenneally , @thibaudteil , what are your thoughts on this ? Thanks =)

[kaisimaoxian]

Hello, may I ask if your problem has been resolved? I also encountered this issue while running the sample program on the official website. The link to the sample program is as follows: https://hanspeterschaub.info/basilisk/examples/scenarioAsteroidArrival.html

[wanglishuo]

I also encountered the same problem. Have you solved it？Do you have any solutions？

[abhinavkrish]

Hi, I am new to Basilisk and I am encountering similar issue with the inbuilt example file, where I am encountering this NOLOADEDFILES error. I have confirmed the files are available in the respective paths as expressed in the scenarioOrbitMultiBody.py. When I run the scenarioSpiceSpacecraft.py, Basilisk runs. Could it be an error in pyswice since scenarioSpiceSpacecraft does not use pyswice.furnsh_c() instead loads the spice kernel directly?

Error from scenarioOrbitMultiBody.py

Toolkit version: N0065
 
SPICE(NOLOADEDFILES) --
 
At least one SPK file needs to be loaded by SPKLEF before beginning a search.
 
A traceback follows.  The name of the highest level module is first.
spkezr_c --> SPKEZR --> SPKEZ --> SPKGEO --> SPKSFS
 
Oh, by the way:  The SPICELIB error handling actions are USER-TAILORABLE.  You
can choose whether the Toolkit aborts or continues when errors occur, which
error messages to output, and where to send the output.  Please read the ERROR
"Required Reading" file, or see the routines ERRACT, ERRDEV, and ERRPRT.

[bbercoviciUspace]

you may want to check whether the file hashes are correct as demonstrated in #211 (comment)

[wanglishuo]

Hello, thank you very much for your reply. May I ask if you have a solution? Can I download the correct file from the official website and replace the mismatched file?

[bbercoviciUspace]

That's how we dealt with the issue, by manually pulling the file from github. I would first check if the hash of de430.bsp is correct, this is the file that got corrupted in our case.

[wanglishuo]

Thank you. My problem has been solved!