search

sot / timelines

Commanded states timelines
3 stars 0 forks source link

Create a complete sqlite version of cmd_states tables #17

Closed taldcroft closed 7 years ago

taldcroft commented 7 years ago

The branch is py3, but this is really just to support no-sybase operation with a single sqlite3 database that has all the relevant tables.

No Py3 compatibility code changes are made.

taldcroft commented 7 years ago

We would need to understand implications for hand processing that gets done.

jeanconn commented 7 years ago

Regarding hand processing, I don't immediately see a way to not archive commands to a archive-file when calling add_nonload_cmds.py. I think that's what we described for the plan (running add_nonload_cmds.py twice to get sybase and sqlite but only archiving the update once).

jeanconn commented 7 years ago

I've just got a throw-away file solution in https://github.com/sot/scs107/pull/1

taldcroft commented 7 years ago

Looks good to me. Have you independently created the new cmd_states.db3 from scratch? Hopefully that worked?

jeanconn commented 7 years ago

Doing that now. ​

jeanconn commented 7 years ago

I made a new db3 per the NOTES and just copied it into /proj/sot/ska/data/cmd_states . I didn't independently verify its content, but I think this is good to go.

jeanconn commented 7 years ago

Independent verification by just running the jobs on it and hoping for the best did not work. The new/copied sqlite database doesn't appear to have the parsed content (tl_built_loads etc) that the update_load_seg routine needs to build new timelines.

I'll make a new PR to fix any outstanding issues. For now, I've just commented the sqlite bits out of the flight task schedule.