---
# System prepended metadata

title: Tudat Developer Meeting 19/03/2022

---

# Tudat Developer Meeting 19/03/2022

## Agenda Items

- Recent project updates
    - New example setup
    - Automated conda build setup
- Outreach
- IAC paper
    - Tudat dissemination actions
    - Moving to tudat.tudelft.nl
- Upcoming feature developments
    - Thrust refactor
    - Integrator update
    - Honours students (non-conservative force modelling)
    - Exception/Error handling & conversion
- Documentation
    - [x] ACTION (FO): Conversion tex to rst files; NB: LaTeX is permissible within rst files

## Minutes

- [x] ACTION (FO): link to tudat space and possibly the API. Link from the "About" sidebar to the mathematical documentation. On tudat-space it's already there; (on the landing page under external resources);

### Examples setup: embedding in code for dynamic examples
- [x] ACTION: open issue on tudatpy examples
Use NBsphinx (?) to embed jupyter notebooks into rst (?); see post on Slack.
- Prefered to have interactive docs/examples
- Check things in the Gallery are not broken.
- Investigate the option for automatic conversion.
- GG: Proposal automate a github workflow
- [ ] ACTION (1 ??, support: GG): create a tudatpy-examples issue for this


Different version of the documentation (described on Slack).
- changelog is available
- is it good to have the versions visible?
- link the version of the documentation (tudat-space) to the tudatpy version? 
    - Proposal (GG): add to release pipeline
- DD: Don't do anything yet. Revisit this in the near future
- [x] ACTION (FO): will write guidelines

### Automated conda build setup
GG created this and gives an overview
idea: automate versioning (on the dev branch)
- a push to tuddat or tudatpy triggers a version increment (including dev); convention is detailed in the documents
- NB: semantic versioning is not python compatible. instead see PEP 440.
- just add the #CI tag anywhere in the commit message; the _last_ commit message
- user releases are found here: https://github.com/tudat-team
- recent changes found under "unstable"
- locally package builds and ??? are checked, so being notified if something goes wrong
- Proposal (GG): sequential building will be updated, eg. so that tudat is built before tudatpy
- Alt proposal (DD): KIS -> Just stagger the builds by some hours and notify users

For the stable release versions
- see checklist on Slack (to be put in dev docs)
    - some items (eg. C++ style) can be automated
- DD: first get the releasing set up
- NB: use rever to (partially) automate the versioning
ACTION (FO, support: GG): transfer guide to dev docs

DD: Prefer to do this in the near future
- Prefer students use release versions not dev versions
- Manually write into changelog for releases (whereas dev changelog is automated with commits)
- Proper versioning supports Outreach
- GG: Add manual notes to the dev history. DD: downside is it's an extra step during development.

Question JG: Does conda update finally work?
- ACTION (JG): reproduce the problem and show GG

### Outreach
#### IAC paper & presentation
- abstract is submitted. Thanks to FO.
    - classed at conference under generic astrodynamics / interactive presentations
    - paper submission approx end-Aug 2022
- Who will go and present?
    - FO intends to go.
- Preparing for the paper:
    - nice to have: link to tudat-space (or wlesehwer) so readers can run it.
    - abstract still focused on different examples.
    - Waht's the main message? Who's the audience?
        - Why is this usable by 'you/future user'?
        - How can you use it in different user-scenarios, missions, ...
- Preparing for the paper:
    - GG: use one example/scenario (asteroid optimisation seems complete enough for this) and build it out during the presentation
- You can simulate many things:
    - environments: reentry, interplan, deorbits, ascent
    - use for: simulate, optimize, estimate, ...

ACTION (All in slack):
How to organize the work:
- TOC
    - identify sections, then divide and conquer
- one person owns each section
- one person (tip: DominiKevin) looks at the overall paper

#### Other dissemination issues
- output from datcom ???

#### Moving to tudat.tudelft.nl
- Idea: use this domain as a landing page
- DD: going to this domain, they should see what's now on tudat-space

### Feature development

#### Two new honor students start Q4 2022, working on:
- rarified flow aerodynamics (Andrea Gonzalez Ramiro (?), MSc student)
        - JG is interested in collaborating on this / contributing what he has
- radiation pressure (BSc student, former CompSci)

- Eelco Doornbos (now Christian & Joao)
    - MRTDMDSEDLJDFFJ thingie 


#### Tune-up of numerical integrators
JG working on this
- more flex step-size control
- other integrators
- simpler interface
- NB: GG has started some refactoring; keep DD in the loupe (Ha!)

#### Exceptions
ACTION: place in agenda for next meeting

Catching exceptions would be good, but during propagation all exceptions should be caught.
Wish: make user output more consistent
DD: this is a big task
FO: wants to collect common errors in a small guide; 
- DD: add 'how to debug'; 
- GG: add "this function can throw error XXX"
