bibbster
Well-Known Member
Wrong thread.
The optimum delay is the time to apogee minus the burn time, so this doesn't sound right. Please post your .ork file so we can take a look at it (I may not be able to look until next week, but the other team members should be around in the mean time).Looking at other motor sims for the same rocket, the optimum delay that is calculated for nearly all the rest is very close to (Time to apogee) - (Burn time). Which seems reasonable. But for the F39W, that would give a delay of 6.67s, not the 7.86s shown on the printout.
If it is a data error, you might also look at the AT 29/40-120 F22J. Shows time to apogee 8.94s, burn time 3.14s, optimum delay 7.31s. If you subtract the burn from the time to apogee, you get 5.8s.
I would love it if there was a way to export the simulation results summary table as a .csv. I tend to try out a lot of motors, and it would be nice to be able to save that table and play with it in Excel. For example, indicating the short list of particularly good matches, highlighting bad ones, adding comments, etc.
I could just delete the bad ones, but then my little terrier brain will want to go back and try them again, which wastes time. I leave them in the file to keep a log of what I've tried that didn't look good, but I'd also like to be able to produce a compact list of just the good ones.
It shouldn't be too hard... I'd generally like he some fancier options -- being able to separate the payload section will be another.I'm wondering how hard it would be to implement an option to 'release' (disable/not count) one chute when a later one is deployed. I'm thinking a checkbox in the design window. Maybe fancier recovery configuration options.
I can't replicate the issue....The optimum delay is the time to apogee minus the burn time, so this doesn't sound right. Please post your .ork file so we can take a look at it (I may not be able to look until next week, but the other team members should be around in the mean time).
Figure it out and submit a pull requestWhere should I go with a feature request? The ability to optimize for delay time would be useful for a few things I’m thinking about.
Where should I go with a feature request? The ability to optimize for delay time would be useful for a few things I’m thinking about.
I've known several people to build a rocket just to get rid of a surplus of a particular motor of a particular delay.What are you thinking of where you would optimize specifically for delay time?
Basically.I've known several people to build a rocket just to get rid of a surplus of a particular motor of a particular delay.
https://github.com/openrocket/openrocket/issues Click on"New"Where should I go with a feature request? The ability to optimize for delay time would be useful for a few things I’m thinking about.
Thank you.
The .jar is still available. We don't foresee changing that."Starting with the 2022 release, we will be distributing OR primarily as a packaged application for Windows, Mac, and Linux."
Gah...
Otherwise good idea.
I'll take a jar any time over an installer... THANK YOU!The .jar is still available. We don't foresee changing that.
The .jar is still available. We don't foresee changing that.
If you have Java 11 installed on your Raspberry Pi, then I think you can run the JAR file. 3D stuff will be non-functional, though (right now it’s x86-specific).
What is required for it to run on ARM, my Raspberry Pi?
Same question for a new Mac using an M1 or M2 ("Apple silicon") processor. I don't have one of these, but after seeing how screamingly fast my wife's new M2 MacBook Air is, I may move replacing this 15 inch MacBook Pro up a bit in priority....f you have Java 11 installed on your Raspberry Pi, then I think you can run the JAR file. 3D stuff will be non-functional, though (right now it’s x86-specific).
I was going to select a yearly contribution but the "same day each month" part confused me, and as much as I love OR, I can't afford to be contributing $600 per year ($50/month) towards it.Contribution Summary
Contribution to OpenRocket$5.00 USD
Today's charge$5.00 USD
If you select PayPal, you will be charged on the same day each month. Otherwise the next charge will be on September 1, 2023 and then the first day of the same month each year. You can cancel or edit this contribution by going to 'Manage Contributions'.
Enter your email address to join: