astrodbtoolkit / astrodbtoolkit/astrodb_utils

Ingesting proper motions

Open
#167 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
0
Forks
10
PR merge metrics
No merged PRs in 30d

Description

I’m working on ingesting a single source that has ra,dec, J,H,K photometry, pm_ra & pm_dec. From the api, there are ingest functions for name, source, photometry, photometry_filter, instrument, and publication. For ingesting things like proper motions, is `ingest_proper_motion` (see https://github.com/SIMPLE-AstroDB/SIMPLE-db/blob/main/scripts/ingests/Gaia/ingest_gaia.py line 151) outdated? I don’t see it in the astrodb_utils github. The other option I see is in the astrodb template’s ingest_pso0318 file where you can directly insert the values to a table
```
with db.engine.connect() as conn:
conn.execute(db.RadialVelocities.insert().values(rv_data))
conn.commit()
```
Is the insert option the right way to go?

Contributor guide

No contributing guide indexed for this repository

Research direction

Compare the ingest functions in astrodb_utils with scripts/ingests/Gaia/ingest_gaia.py around line 151 and the astrodb template’s ingest_pso0318 example. First determine whether proper-motion ingestion is still supported, then establish and document the accepted path for inserting pm_ra and pm_dec values. Done means the supported approach is clear and tested against the relevant database table.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.