-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recreate complete history for all languages #1
Comments
Thanks for the idea @ckuethe! With a little bit of patience and help from web.archive.org we could do the same thing here, for all languages (and not only the ones I cared about when I created this repo). |
I have already retrieved historical versions... https://drive.google.com/open?id=1L_PFk6dUDk4G5fPMoMb7C1CBbDTwX1P0 |
That's super helpful 😍 I'll put it into the repository tomorrow! |
Tagging @interplanetarychris @brandon-rhodes @rirze @cbassa because they would probably also be interested in this based on their participation with skyfield and python-sgp4 |
@Juanlu001 Seems like this repository is aiming to be more complete wrt to Vallado's work implemented in many languages. I'm willing to merge/retire my mirror (rirze/sgp4-cpp) if you end up recreating the c++ history. Just let me know either way. |
I definitely like the way you synthesized authors and timestamps. |
@ckuethe Thanks. It was a bit of effort to figure out how to do it at first. In case you want to do it the same way I did @Juanlu001, here's the command I used: THE_TIME=$(stat -c %y $(find cpp/ -type f -printf "%T@ %p\n" | sort -n | sed -r "s/^[0-9.]+\s+//" | tail -n 1 | xargs -I{} ls "{}")) GIT_AUTHOR_DATE=$THE_TIME GIT_COMMITTER_DATE=$THE_TIME git commit -a --author="David A. Vallado <[email protected]>" There's a lot of logic to find the latest file timestamp, but other than that, iterating through the historical versions after deleting the old one was all there was to it. |
I see that there are a lot of repositories that try to do this, but none of them has the full, proper commit history as we would like. I will try to tackle this during the summer. |
@astrojuanlu Could you expand on what that includes? Where are other approaches or repositories lacking? |
Sorry for the delay - I've seen countless repositories that copy paste Vallado software from the website, but what we would like to do here is to rebuild a sort of "commit history" using the updates and the changelogs from the source itself, so we can also see differences between versions.
GitHub <[email protected]> wrote:
“
@astrojuanlu Could you expand on what that includes? Where are other approaches or repositories lacking?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.”
|
Sorry @rirze, the other day I responded too quickly and didn't realize we had already spoken in this same thread last year :) It's been a tough winter. Okay, so the two things I would like to have is:
I'm working on this as part of the SciPy US 2020 sprints, hope to get at least a prototype working. |
@ckuethe, @rirze, I have two files from the 2004 era which might be of use for C++ and FORTRAN tests. Their content listings follow. Would these help, and if so, how do I get them to you? Archive: sgp4c.zip
359608 07-22-2004 09:30 SGP4TEST.TXT 851460 8 files Archive: fortran-data.zip
101257 04-03-2003 07:10 TESTASTF.TXT 320741 16 files |
You might want to check out similar repos - history has been reconstructed from older versions of the software, eg. https://github.com/rirze/sgp4-cpp
The text was updated successfully, but these errors were encountered: