Summary of Talk

• Description of why opacities are needed for exoplanet science
• Description of how opacities are calculated
• Description of the bottlenecks to computing opacities
• Description of MAESTRO team goals
• Questions posed to the community
  1. What data products should be given highest priority?
  2. What code features are needed?
  3. What new molecules do you need?

Summary of Discussion

• DOI's for database entries: Beyond providing citations for each data bundle, it was suggested that we also create a formal DOI system. Thoughts?
• Correlated-K's: There was a push for providing Correlated-K tables (in addition to code) but we'd have to think about how to service this. The comment came from Shawn Domagal-Goldman, who is focused on terrestrial atmospheres, so that in and of itself would be tricky.
• Aggregated Line List DB: Huge push for aggregated line list database that has "best practices" line lists to use. We need to make sure that this is carefully priced out on AWS before forming aggreing to do this.
• No suggestions for new molecules. There was a inquiry into hosting other kinds of optical data (e.g. cloud species). I said that no for now...

Done:

1. Built initial SQL database
2. Code for appending HITRAN data
3. Code for appending ExoMol data
4. Bulk insert into database to improve permormace
5. Auto import data using HAPI and Beautiful Soup for ExoMol

Up Next:

1. Optimize code
2. Turn scripts into code package