Skip to content

Mass optimisation has negative reference value in 'def add_objective' in 'interface\methods_for_level2.py' #899

@jexalto

Description

@jexalto

Hey Aviary team,

I was going over some of the examples, and for the run_battery_mission.py (examples\external_subsystems\battery\run_external_battery_mission_example.py) when we optimise for 'mass' (landing mass) the reference value becomes negative (link added below). The mass is therefore maximised instead of minimised.
I'm not sure if this is the intention and I am not understanding something, or that this should perhaps be a positive value?

Joaquin Exalto
(Elysian Aircraft Team)

default_ref_values = {

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions