Eliot Aretskin-Hariton

Results 13 comments of Eliot Aretskin-Hariton

To calculate `ALTITUDE_RATE_MAX` we need supporting information: - `Dynamic.Mission.THRUST_MAX_TOTAL`, - `Dynamic.Mission.VELOCITY` = `TAS` - `Dynamic.Mission.VELOCITY_RATE` = `TAS_rate` - `Dynamic.Mission.MASS`, - `Dynamic.Mission.DRAG`. Functions are already defined in FLOPS for calculating `SpecificEnergyRate()`...

For Reserve Phases, or phases with `target_time = True`, we need much fewer inputs than is currently listed in `check_phase_info|common_entries`. Items like `fix_duration`, `duration_bounds`, and `initial_guesses|times` can be safely ignored...

Additionally, tests in the examples folder will need to be revised once this work is completed to remove the extra inputs: `run_reserve_mission_cruise_fixedrange` `run_reserve_mission_cruise_fixedtime` `run_reserve_mission_multiphase_fixedrange` `run_reserve_mission_multiphase_fixedtime` `run_reserve_mission_multiphase_time_and_range` assuming that all of...

Recent experiences with new users modifying phase_info revealed a lack of documentation for how the current functions really work. initial_bounds - the is the absolute start time of the phase,...

Currently, modifying the `phase_info` is one of the easiest ways to break an optimization. I believe that in the long-term, we should limit interactions with `phase_info` to graphical-based tools for...

Some checks on phase_info exist in methods_for_level2 and some exist in check_phase_info, these should be consolidated to all exist in check_phase_info.

pre and post mission are not being checked for valid keys. This has caused incorrect keys like `"constrain_range": True,` to be retained in the examples even though it has no...

`polynomial_control_order` is not in check_phase_info or methods_for_level2. I believe it is required because it's used in flight_phase_builder, but it's not throwing an error (which it should if it's not on...

Had this issue with my Prusa Mini (100% genuine parts) pre-upgrading to 4.4. Temp on the fillament heater was unable to get past 212 degrees and fillament was stuck half-way...

Follow-up. I kept having these errors till I replaced the original thermister that came with the unit with another one also ordered from Prusa. Software wasn't the issue.