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

Exception when trying to reconcile cached files during LDPSetCreator init #28

Open
jpl-jengelke opened this issue Dec 1, 2022 · 2 comments

Comments

@jpl-jengelke
Copy link
Contributor

jpl-jengelke commented Dec 1, 2022

File "c:\users\pablo\appdata\local\programs\python\python39\lib\site-packages\exotic\api\gael_ld.py", line 97, in createldgrid
    sc = LDPSetCreator(teff=(tstar, terr), logg=(loggstar, loggerr),
  File "c:\users\pablo\appdata\local\programs\python\python39\lib\site-packages\ldtk\ldtk.py", line 425, in __init__
    with pf.open(self.files[0]) as hdul:
IndexError: list index out of range

Client.__init__() on line 415 calls self.set_limits() which in certain cases results in client.files being empty. So when the property client.local_filenames is used it can return an empty list. Then the call to pf.open(self.files[0]) in LDPSetCreator.__init__() raises an exception because it's operating on an empty list.

I don't have much more information on why the set of files is empty in the first place, but perhaps we can get a use case to help troubleshoot this. It is currently being exposed by the EXOTIC product in certain very limited circumstances.

@jpl-jengelke
Copy link
Contributor Author

jpl-jengelke commented Dec 1, 2022

This is currently exposed in LDTk v1.7.0 and exercised in EXOTIC 2.3.0.

The line that invokes the issue is at https://github.com/rzellem/EXOTIC/blob/2.3.0/exotic/api/gael_ld.py#L97

@jpl-jengelke
Copy link
Contributor Author

jpl-jengelke commented Dec 1, 2022

Adding EXOTIC inits and error files. ...
LDTk_exception_EXOTIC_2-3-0.txt
inits_24_11_2022__16_15_35.json.zip

Explanation: This was exposed by "an unphysical value that was marked by NEA - once manually overrode, then things were fine again. ... TL;DR - A bad value was found in the NEA entry for this target."

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

No branches or pull requests

1 participant