Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

spiceinit problem with user DEM if using web kernels #4034

Closed
Ben-Bussey opened this issue Sep 24, 2020 · 6 comments
Closed

spiceinit problem with user DEM if using web kernels #4034

Ben-Bussey opened this issue Sep 24, 2020 · 6 comments

Comments

@Ben-Bussey
Copy link

ISIS version(s) affected: 4.1.2

Description
I get a smear model error if I try and use a local DEM. I can run spiceinit on a LROC WAC cube (output from lrowac2isis) with web=yes for the SPICE. But if I choose SHAPE=USER and point to a local DEM I get an error (attached) about initializing a camera model. The DEM I am using has been through DEMPREP.

As a test I went and selected the DEM that is installed in the base/dem directory, which is the one that spiceinit uses if you leave shape=system. I get the same error

How to reproduce
process a WAC CDR through lrowac2isis, to get an odd and even cube. then try and run that cube through spiceinit using web=yes for the spice, and a local dem
Screen Shot 2020-09-24 at 3 19 46 PM

Possible Solution

Additional context

@jessemapel
Copy link
Contributor

This is an unfortunate side effect of how the spice web server works. It basically runs spiceinit with your image label on our server that has the data area. So, anything that uses a local path for your system will not work with the spice web server.

For Surface models, there is potential to make this work. See #1986

@jessemapel
Copy link
Contributor

I'm going to leave this open for adding a better error message because it's easy to check for this case.

@jlaura
Copy link
Collaborator

jlaura commented Sep 24, 2020

@kberryUSGS I believe that working on making this work with the SPICE server is out of scope for the calibration routines. Does it make sense to label this as a SPICE server related issue as we transition (longer term) to fully supporting remote SPICE?

@jlaura
Copy link
Collaborator

jlaura commented Sep 28, 2020

It looks like this should have been fixed already via #3791. We need to redeploy those changes for the SPICE server. Thanks @Kelvinrr for identifying that merged PR for me!

@Kelvinrr
Copy link
Collaborator

@jlaura that PR addresses the version issue (this seems more like a duplicate of #1986, not #3725), so I don't think that PR affects this problem at all (oddly enough, before the fix was deployed I'm surprised he got to the camera model init step using 4.x.x 🤔 ).

@jessemapel jessemapel modified the milestone: 4.3.1 Dec 14, 2020
@jessemapel
Copy link
Contributor

After more discussion we're going to close this in favor of #1986. Basically the amount of work required to add an exception is low, but the amount of work to make this just work isn't that much more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants