Shape Mismatch for WING_LOCATIONS with NUM_WING_ENGINES = 0 #781
Unanswered
OscarEspinosaBarcenas
asked this question in
Q&A
Replies: 2 comments 2 replies
-
Hi Oscar, thanks for reaching out! This error looks familiar, I remember we previously had issues with setting single engines before so this may be related. I will poke around and see if I can figure out where that incorrect shape is getting set by the IVC! |
Beta Was this translation helpful? Give feedback.
0 replies
-
@OscarEspinosaBarcenas try updating your Aviary install to at least 0.9.9, that should include the fix that will solve this error. This is the specific fix in question: #709 |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi Aviary Team,
I'm working with Aviary 0.9.8 in WSL and trying to model an aircraft with a single fuselage-mounted engine. I've set the following inputs:
I have not explicitly set
Aircraft.Engine.WING_LOCATIONS
in my inputs, as there are no engines on the wings.When I run
prob.setup()
, I encounter thisRuntimeError
:It seems that even with
NUM_WING_ENGINES = 0
(which should correctly make the target shape forwing_locations
be(0,)
), an auto-IVC is still attempting to provide a scalar default (source shape(1,)
) forwing_locations
, leading to the mismatch.Could you please advise on the recommended way to configure
WING_LOCATIONS
(or related settings) whenNUM_WING_ENGINES = 0
to avoid this shape conflict during prob.setup()?Thanks,
Oscar
Beta Was this translation helpful? Give feedback.
All reactions