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

Error: could not get spaxel #391

Closed
AMWeijmans opened this issue Mar 13, 2018 · 2 comments
Closed

Error: could not get spaxel #391

AMWeijmans opened this issue Mar 13, 2018 · 2 comments
Assignees
Labels
bug a general bug or other breaking feature priority-high vetting indicates issues found during dedicated vetting sessions
Milestone

Comments

@AMWeijmans
Copy link

For galaxy 8141-6101: when toggling map view, I get:

Error : Error: Could not get spaxel: No row was found for one()

However, if I then select DAP maps to display, they do show.
This also happened for galaxy 8250-3702, all other galaxies I looked at were fine.

@havok2063 havok2063 self-assigned this Mar 14, 2018
@havok2063 havok2063 added bug a general bug or other breaking feature priority-high labels Mar 14, 2018
@havok2063 havok2063 added this to the Feedback milestone Mar 14, 2018
@havok2063
Copy link
Collaborator

Thanks, Anne-Marie. Digging into this a bit it seems the fundamental issue is that the DAP model cube spaxels for these galaxies (and about 30 others) for MPL-6 did not get loaded in the database. So the web-spaxel view fails because it's trying to find and plot the model fits when they don't exist. Thanks for finding this. I'll load them in and let you know when things are fixed.

@havok2063 havok2063 added the vetting indicates issues found during dedicated vetting sessions label Mar 19, 2018
@havok2063
Copy link
Collaborator

I've now added all the model spaxels into the database for all the missing galaxies, ~30 SPX and ~30 HYB10. You should now be able to see and use the map/spec view on the web for these galaxies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug a general bug or other breaking feature priority-high vetting indicates issues found during dedicated vetting sessions
Projects
None yet
Development

No branches or pull requests

2 participants