You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the "Future of Exoplanet Watch" meeting which occurred on March 15th, 2024, a suggestion was made to potentially enhance the descriptiveness of any errors in EXOTIC. For example, when a user is not able to obtain a plate solution for their data set, how might this impact them? Some of us are aware of what the plate solution does with respect to EXOTIC and some aren't. Would it be beneficial for us to create a list of all respective errors that might happen, whether the error is significant enough to stop EXOTIC from running or not, how it might impact the results if EXOTIC continues and produces a light curve or not, etc.? That list could then be implemented in the code to display in Google Colab (or wherever a user chooses to use EXOTIC).
The text was updated successfully, but these errors were encountered:
On the "Future of Exoplanet Watch" meeting which occurred on March 15th, 2024, a suggestion was made to potentially enhance the descriptiveness of any errors in EXOTIC. For example, when a user is not able to obtain a plate solution for their data set, how might this impact them? Some of us are aware of what the plate solution does with respect to EXOTIC and some aren't. Would it be beneficial for us to create a list of all respective errors that might happen, whether the error is significant enough to stop EXOTIC from running or not, how it might impact the results if EXOTIC continues and produces a light curve or not, etc.? That list could then be implemented in the code to display in Google Colab (or wherever a user chooses to use EXOTIC).
The text was updated successfully, but these errors were encountered: