NOTE: This Tudat version is no longer supported. See https://docs.tudat.space/en/stable/ and https://github.com/tudat-team/tudat-bundle for the new version
Making a fresh clone of tudat can take...quite a while. Running ncdu on tudat/ shows why:
There's a few ways to improve this situation:
Have git-lfs manage them. This is probably the lowest hanging fruit. With git-lfs, at least diff'ing stuff will be faster, and the repository db (i.e., the .git folder) will be significantly smaller. Drawback: that's yet another dependency, needs a documentation change, and is fairly easy to screw up (also, ideally, you'd git lfs migrate the whole repository (rewriting history + force push), which is not without its risks, but this can be skipped)
create some CMake targets that downloads/generates these files on the fly (e.g., CSPICE kernels are not needed if USE_CSPICE is off). This is probably the nicest way to deal with this sort of thing, but requires the most effort.
Something I didn't think of 😊
I'm happy to help out; I just need to know what to do.
Making a fresh clone of
tudat
can take...quite a while. Runningncdu
ontudat/
shows why:There's a few ways to improve this situation:
git-lfs
manage them. This is probably the lowest hanging fruit. Withgit-lfs
, at least diff'ing stuff will be faster, and the repository db (i.e., the.git
folder) will be significantly smaller. Drawback: that's yet another dependency, needs a documentation change, and is fairly easy to screw up (also, ideally, you'dgit lfs migrate
the whole repository (rewriting history + force push), which is not without its risks, but this can be skipped)USE_CSPICE
is off). This is probably the nicest way to deal with this sort of thing, but requires the most effort.I'm happy to help out; I just need to know what to do.