search

convexengineering / SPaircraft

Models for commercial aircraft design
http://spaircraft.readthedocs.org
25 stars 17 forks source link

Unused variables in VT, HT and Wing #15

Closed 1ozturkbe closed 7 years ago

1ozturkbe commented 7 years ago

I was running CFP_Fuselage_Performance_int_HT.py bounded when I realized some variables were going off to 1e30. The reason for this is that the variables don't show up when Bounded is not used because there are no constraints that involve these variables. But when Bounded is engaged, they show up! This is not very user-friendly, and we should remove these unnecessary variables.

The variables are a subset (perhaps all) of the variables found in this Bounded solve output. 


Solves with these variables bounded:
   value near upper bound: [M_Mission.11, ClimbSegment.11, ClimbP.11, AircraftP.22, WingPerformance.22_(0,), K_f_Mission.11, Aircraft.11, HorizontalTail.10, HorizontalTailNoStruct.10, g_Mission.11, ClimbSegment.11, FlightState.22, Atmosphere.22_(1,), g_Mission.11, CruiseSegment.11, FlightState.23, Atmosphere.23_(1,), \rho_c_Mission.11, Aircraft.11, VerticalTail.11, VerticalTailNoStruct.11, W_0_Mission.11, ClimbSegment.11, ClimbP.11, AircraftP.22, WingPerformance.22_(0,), t_{web}_Mission.11, Aircraft.11, Wing.11, WingNoStruct.10, M_Mission.11, CruiseSegment.11, CruiseP.11, AircraftP.23, WingPerformance.23_(0,), W_{vt}_Mission.11, Aircraft.11, VerticalTail.11, VerticalTailNoStruct.11, W_0_Mission.11, CruiseSegment.11, CruiseP.11, AircraftP.23, WingPerformance.23_(0,), C_{L_{vt}}_Mission.11, CruiseSegment.11, CruiseP.11, AircraftP.23, VerticalTailPerformance.22_(0,), W_0_Mission.11, ClimbSegment.11, ClimbP.11, AircraftP.22, WingPerformance.22_(1,), x_w_Mission.11, Aircraft.11, Wing.11, WingNoStruct.10, M_Mission.11, CruiseSegment.11, CruiseP.11, AircraftP.23, WingPerformance.23_(1,), t_{cone}_Mission.11, Aircraft.11, Fuselage.11, g_Mission.11, CruiseSegment.11, FlightState.23, Atmosphere.23_(0,), g_Mission.11, ClimbSegment.11, FlightState.22, Atmosphere.22_(0,), C_{L_{vt}}_Mission.11, ClimbSegment.11, ClimbP.11, AircraftP.22, VerticalTailPerformance.21_(0,), p_{\lambda_v}_Mission.11, Aircraft.11, VerticalTail.11, VerticalTailNoStruct.11, C_{L_{vt}}_Mission.11, ClimbSegment.11, ClimbP.11, AircraftP.22, VerticalTailPerformance.21_(1,), taper_Mission.11, Aircraft.11, Wing.11, WingBox.31, C_{L_{vt}}_Mission.11, CruiseSegment.11, CruiseP.11, AircraftP.23, VerticalTailPerformance.22_(1,), W_0_Mission.11, CruiseSegment.11, CruiseP.11, AircraftP.23, WingPerformance.23_(1,), M_Mission.11, ClimbSegment.11, ClimbP.11, AircraftP.22, WingPerformance.22_(1,), taper_Mission.11, Aircraft.11, VerticalTail.11, WingBox.32, t_{cap}_Mission.11, Aircraft.11, Wing.11, WingNoStruct.10]```
1ozturkbe commented 7 years ago

The output is from commit 356e00e, CFP_Fuselage_Performance_int_HT.

1ozturkbe commented 7 years ago

As of commit 9b6242c, all variables in D8_VT are bounded (involved in useful constraints). HT and Wing still need work.

1ozturkbe commented 7 years ago

As of commit 423caa09, all variables in Wing_simple_profile are involved in useful constraints.

1ozturkbe commented 7 years ago

As of commit b93c5c5e, all variables in D8_HT bounded by constraints as well. Can now close.