Skip to main content


Open source software costs nothing, but enables people to do great things with it. This is the #opensource software/data I've been using to create maps, process images, make animations etc. related to #NASA's #Mars2020 mission:

#GIMP : gimp.org
#Geogebra : geogebra.org
#ImageMagick : imagemagick.org
#QGIS : https : qgis.org
#Stellarium : stellarium.org

@kevinmgill's and @stim3on's flats: github.com/kmgill/mars-raw-uti…

1/

Astro Migration reshared this.

in reply to 65dBnoise

Aurélien Genin's image correction scripts: github.com/AstroAure/Ingenuity…

and of course, #NASA's:

Mars24 Sun clock: giss.nasa.gov/tools/mars24/

Mars2020 MMGIS map: mars.nasa.gov/maps/?mission=M2…

Mars2020 images: mars.nasa.gov/mars2020/multime…

#HiRISE ortho map: astrogeology.usgs.gov/search/m…

Of course, nothing much would have been done, had it not been for the JSON and GeoJSON feeds provided by #NASA through the Mutli-Mission Geographical Information System, MMGIS: (JSON links follow)

2/

in reply to 65dBnoise

@65dBnoise

Just curious... Have you ever seen a way of converting Earth date time to Mars sol / time in a spread sheet? :)

in reply to Paul Hammond

@PaulHammond51
Not in a spread sheet, but I don't see why that can't be done. The calculations involved can be entered in cells and yield results, if one has patience and is careful enough when entering formulas 😬

I added the link to the math in the sources: mastodon.social/@65dBnoise/109…

in reply to 65dBnoise

@65dBnoise
thanks, I will see if I can get my head around that math (not my strong point LOL) and format it as a formula
in reply to Paul Hammond

@PaulHammond51
Oh, no, not one formula, many formulas, each one yielding a specific parameter (needing a sanity test too because you may go insane while doing it 😬 😬 ).
All of the individual formulas combine, step after step, to give various results, one of which should be what you are looking for 😩
Unfortunately the universe is an analog world, and this is an approximation of a tiny part of it, thanks to M. Allison.
in reply to 65dBnoise

@65dBnoise

Seemed like a good idea at the time.... Will look for another way :)

in reply to Paul Hammond

@PaulHammond51
If you can run the Mars24 Sun Clock (Java needed), that has an input to convert UTC to MST etc
in reply to 65dBnoise

@65dBnoise

Not sure if that's possible to run that inside my spread sheet, but I will look into it, as I would really like to add an accurate 'Earth dates' to each new drive by a rover, without having to do it manually (my present method)

I'm chewing over a method that uses 'CONCATENATE' to extract the UTC (MM/DD/YYYY) from the first image acquired at new site/drive (date_taken_utc) but even that looks like it needs a series of steps

in reply to Paul Hammond

@PaulHammond51
Oh, I forgot the spreadsheet. I'm afraid the Mars24 idea requires manual entry of data. I don't think it's suitable for auto spreadsheet calculations. Getting the Mars24 output into a spreadsheet will be a challenge, too.

Spreadsheets are handy tools, but unfortunately not for everything.

in reply to 65dBnoise

@65dBnoise

Agreed, they are a very useful tool, but like most things in life, they all have limitations :)

in reply to Paul Hammond

@PaulHammond51 @65dBnoise fascinating to me that there's not a readily available API with Mars24 functions. I saw that there's a sort of javascript port attempt that hasn't seen much love for a while (rows 448 and forward, e.g. row 503 has the perturbers table from step B-3 in the Mars24 algo)

github.com/jtauber/mars-clock/…

in reply to V Martín

@sharponlooker @PaulHammond51
Crediting, boosting, appreciating may be a way to extract more "readily available API"s out of those altruistic enough to spend the time, in the world of "free as in 'free beer' and in 'free speech'". Donating works also, most of the time :-)
in reply to 65dBnoise

@65dBnoise @PaulHammond51 absolutely, but isn't this a NASA app, wouldn't mission teams want that api? I was just surprised it wasn't already among NASA's list of public apis
in reply to V Martín

@sharponlooker For a Javascript API/lib the need might exist if an online page showed local time (not UTC) live or related to events, but AFAICT none does.

The hard part with software (even more so with *free* software) is not writing code that does the job, but maintaining it when it's out in the public, keeping track of and fixing bugs, adapting it to the changing environment it being used in, keeping track of and updating dependencies etc.

in reply to 65dBnoise

@65dBnoise tell me about it, lifecycle management is a PITA but oh so important & costly 😉

I was approaching this case more from @PaulHammond51 's perspective, I guess his spreadsheet could do with a relatively simple API function call with just one parameter (Earth time), perhaps one more (Mars mission?). This being an established algorithm, the API would be rather static. But of course, if it has to cater for all possible combinations, you have to call the cavalry 😉

in reply to V Martín

@sharponlooker @PaulHammond51
If you count the variables in the algorithm, that's approximately the number of inputs that are needed. Some are fixed, others may temporarily be considered fixed. There is also a great number of outputs, not all of which may be needed, but all have to be calculated, just to be able to tell the time on Mars. Will you need the Sol in a mission for a UTC? Ha ha, you need to input the landing details for each mission. And so on so forth.