-
Notifications
You must be signed in to change notification settings - Fork 23
Ingest astronomical properties of ultracool benchmarks #657
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
base: main
Are you sure you want to change the base?
Conversation
I have a lot more json files changed because it reordered the parameters of each JSON file for some reason... I think it might be the order of the parameters I ingested in this script because its different than the other modeled parameters script..? But it's not like any of the existing data changed or got removed because the pytest cases made sense accordingly with the counters. You also might want to take a look at the csv file for missing sourcenames because it is definitely more than before. Not sure how I would just ingest the source since the csv file doesn't provide ra and dec data anyway |
Great start! Two things
|
This reverts commit c2100e4.
I just pushed a few JSON files with the new csvs and pytest and everything |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about using the sigfig package to round the values? https://sigfig.readthedocs.io/en/latest/api.html#uncertainty-u
I'm fine with that, how much should I cut off by? |
This reverts commit a7bad0f.
Just pushed a few json files. I assumed for sigfig the cut off to be 2 decimal places based off other sources in the db. Also please look at my github comment for the eri-b (cold start). There is already an eri-b source with different data values in the same csv file so not sure if I should still change it to eri-b |
51 Eri b (cold-start),"no source found, L6T6" | ||
51 Eri b (cold-start),"no source found, L6T6" | ||
SDSS J105213.51+442255.7A,"no source found, L6T6" | ||
SDSS J105213.51+442255.7A,"no source found, L6T6" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SDSS J105213.51+442255.7
SDSS J105213.51+442255.7A,"no source found, L6T6" | ||
SDSS J105213.51+442255.7A,"no source found, L6T6" | ||
SDSS J105213.51+442255.7A,"no source found, L6T6" | ||
2MASSW J1728114+394859B,"no source found, L6T6" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2MASS J17281150+3948593 is in the database, but no companions. Maybe open a new issue or add the companion and companion relationship.
2MASS J14044948-3159330A,"no source found, L6T6" | ||
2MASS J14044948-3159330A,"no source found, L6T6" | ||
2MASS J14044948-3159330A,"no source found, L6T6" | ||
epsilon IndiBa,"no source found, L6T6" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
epsilon IndiB
WISE J072003.20-084651.2B,"no source found, L6T6" | ||
WISE J072003.20-084651.2B,"no source found, L6T6" | ||
WISE J072003.20-084651.2B,"no source found, L6T6" | ||
epsilon IndiBb,"no source found, L6T6" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
open a new issue or add new companion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks great!
- go ahead and push the JSON files since there's only ~60 of them.
- investigate each source in the "no source" table and see what's up. Either figure out how to ingest or open issues. Search for the sources in the Names table of the sqlite file.
Short description: Include what type of data being ingested and appropriate references.
Link to relevant issue: Closes #110
For data ingests:
[ ] includes script used for ingest
[ ] includes modified JSON files
[ ] Add new tests
[ ] Update the Versions table