Open aashiyashaji opened 1 year ago
Hi @aashiyashaji Yes this looks like a real bug. The stellar continuum extension wasn't in earlier releases of the data, but was added later. Looks like the check on valid model cube extensions never got updated. I'll see about pushing a fix. In the meantime, you can still access the stellarcont_fit
parameter if you load your model cube locally from a file.
Hello, I am quite new to Marvin and was trying to obtain the stellar continuum fit from the ModelCube using the following code:
from marvin.tools.modelcube import ModelCube modelcube = ModelCube(plateifu = '7977-12701', bintype='HYB10') st = modelcube.stellarcont_fit
which raises the following error:
HTTPError Traceback (most recent call last) File ~/opt/anaconda3/lib/python3.9/site-packages/brain/api/api.py:201, in BrainInteraction._checkResponse(self, response) 200 try: --> 201 isbad = response.raise_for_status() 202 except requests.HTTPError as http:
File ~/opt/anaconda3/lib/python3.9/site-packages/requests/models.py:960, in Response.raise_for_status(self) 959 if http_error_msg: --> 960 raise HTTPError(http_error_msg, response=self)
HTTPError: 422 Client Error: UNPROCESSABLE ENTITY for url: https://dr17.sdss.org/marvin/api/modelcubes/7977-12701/HYB10/MILESHC-MASTARSSP/extensions/stellar/
During handling of the above exception, another exception occurred:
BrainError Traceback (most recent call last) File ~/opt/anaconda3/lib/python3.9/site-packages/marvin/tools/modelcube.py:389, in ModelCube._get_extension_data(self, name, ext) 388 try: --> 389 response = self._toolInteraction( 390 url.format(name=self.plateifu, 391 modelcube_extension=model.fits_extension(ext).lower(), 392 bintype=self.bintype.name, template=self.template.name), 393 params=params) 394 except Exception as ee: ... Validation Errors: {'validation_errors': {'modelcube_extension': ['Must be one of: flux, ivar, mask, model, emline, emline_base, emline_mask.']}}. You can submit this error to Marvin GitHub Issues (https://github.com/sdss/marvin/issues/new). Fill out a subject and some text describing the error that just occurred. If able, copy and paste the full traceback information into the issue as well.
I tried this for a few galaxies from DR17 and DR15, however, all gave the same error. Any help would be much appreciated!