I'm about 5 years late to the party here, but I just made a Porkchopper tool on Flight Club. It includes most basic functionality. Does the maths in the client so should be pretty easy to use and responsive tooTry running some plots first with the granularity set to a high number (perhaps 7 or 14 days). Then when you get a feel for the dates and travel times you're interested in, refine those fields and lower the granularity down to whatever you want. That way, you don't spend ages waiting for your browser to solve a bunch of redundant Lambert iterationshttps://flightclub.io/porkchopper
the plotting program I used to use has gone awol
Quote from: waveney on 05/16/2024 08:09 pmthe plotting program I used to use has gone awolIf you're referring to EasyPorkchop written by Juan Luis Gonzalo at UPM, it's still available (for now) on Archive.org.https://web.archive.org/web/20240115183644/http://sdg.aero.upm.es/index.php/online-apps/porkchop-plotYou can also download a local copy, which doesn't rely on any website remaining available. I would highly recommend doing this. I have also attached a backup copy to this post, as it's licensed GPL v3.Locally runnable copy available here: https://web.archive.org/web/20240115183644/http://sdg.aero.upm.es/ONLINEAPPS/Lambert/SDG_EasyPorkchop_1.0.0.zip
I think I found out why the porkchop simulators limit the deltaV range.There's something oddly wrong when you go to large deltavs.Here's what I changed in the code to get higher deltaVs. I get an intermediate high deltaV departure window that at 20km/sec claims 10 days... doesn't seem right.here's the code for a deltaV range of 10km/sec: var levelsStep = [ 0, 1.0, 2.0 , 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0 ] // Values for the contour levels , colors = [ "#4ba7fc", "#3d93ff", "#137bff", "#13ff9b", "#00e785", "#00e01f", "#42c700", "#c76300", "#c71700", "#a40000" ] // Colors for the contour levels , ndim = 300 // Grid size in departure time , mdim = 300 // Grid size in time of flight , DVrange = 10; // Maximum Delta-v range [km/s]
Quote from: InterestedEngineer on 05/18/2024 11:02 pmI think I found out why the porkchop simulators limit the deltaV range.There's something oddly wrong when you go to large deltavs.Here's what I changed in the code to get higher deltaVs. I get an intermediate high deltaV departure window that at 20km/sec claims 10 days... doesn't seem right.here's the code for a deltaV range of 10km/sec: var levelsStep = [ 0, 1.0, 2.0 , 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0 ] // Values for the contour levels , colors = [ "#4ba7fc", "#3d93ff", "#137bff", "#13ff9b", "#00e785", "#00e01f", "#42c700", "#c76300", "#c71700", "#a40000" ] // Colors for the contour levels , ndim = 300 // Grid size in departure time , mdim = 300 // Grid size in time of flight , DVrange = 10; // Maximum Delta-v range [km/s]There's... a lot of limitations in Easy Porkchop. The main one is that the accuracy is terrible, thanks to a limited number of refinement iterations. But even just updating it to modern Javascript and doing some minor refactoring can lead to large speedups.And yes, for efficiency Easy Porkchop will "prune" any solutions that are >10 km/s (vinfinity) above the 'optimal' solution, as found by a sparse 50x50 grid search (see the Javascript function GlobalDVminEstimator in the file LambertSDG-1.0.0.js).
Yes, the Easy Porkchop errors get larger the further you get from the "peak" of the porkchop (which is normally not a big concern). This is discussed in the accompanying paper.
Quote from: Twark_Main on 05/18/2024 11:30 pmQuote from: InterestedEngineer on 05/18/2024 11:02 pmI think I found out why the porkchop simulators limit the deltaV range.There's something oddly wrong when you go to large deltavs.Here's what I changed in the code to get higher deltaVs. I get an intermediate high deltaV departure window that at 20km/sec claims 10 days... doesn't seem right.here's the code for a deltaV range of 10km/sec: var levelsStep = [ 0, 1.0, 2.0 , 3.0, 4.0, 5.0, 6.0, 7.0, 8.0, 9.0, 10.0 ] // Values for the contour levels , colors = [ "#4ba7fc", "#3d93ff", "#137bff", "#13ff9b", "#00e785", "#00e01f", "#42c700", "#c76300", "#c71700", "#a40000" ] // Colors for the contour levels , ndim = 300 // Grid size in departure time , mdim = 300 // Grid size in time of flight , DVrange = 10; // Maximum Delta-v range [km/s]There's... a lot of limitations in Easy Porkchop. The main one is that the accuracy is terrible, thanks to a limited number of refinement iterations. But even just updating it to modern Javascript and doing some minor refactoring can lead to large speedups.And yes, for efficiency Easy Porkchop will "prune" any solutions that are >10 km/s (vinfinity) above the 'optimal' solution, as found by a sparse 50x50 grid search (see the Javascript function GlobalDVminEstimator in the file LambertSDG-1.0.0.js).I'm pretty good at Javascript. If I can get a "source of truth", I'd be happy to spend some time hacking this up and putting it on Github.It needs some unit tests.