marvin
marvin copied to clipboard
better implementation of remote spaxel (flux and property) extraction
Is your feature request related to a problem? Please describe.
Many people are looping over spaxels in a cube or maps to extract many spaxel properties and hitting our API rate limit of 200 calls/minute. And returning the entire cube.flux
has the potential to hit our 5 minute API request timeout. This slowdown may be caused mainly by cube reconstruction rather than returning a json of all the spaxels.
Describe the solution you'd like An efficient way of remotely extracting and returning chunks of spaxel spectra and/or properties.
Either implementation of the cube slicing to extract chunks of spaxels or some method of remotely returning all map properties remotely at once. Possibly reimplement the old spaxel API calls to remotely deal with spaxels directly rather than through tools. Possibly improve API request streaming. Many people are still using the remote mode so just using local files is not a good solution.
Describe alternatives you've considered We've discussed this before and comments are scattered across a few issues and slack history. We should discuss again.