Uploaded image for project: 'GMAT'
  1. GMAT
  2. GMT-3816

Command Mode Clarification for Powered Flight and Solver Infrastructure Feature Groups

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: P2
    • Resolution: Unresolved
    • Affects Version/s: R2014a, R2015a, R2016a, R2017a, R2018A
    • Fix Version/s: Someday
    • Component/s: Thruster (FRR-9)
    • Labels:
      None

      Gliffy Diagrams

        Attachments

          Issue Links

            Activity

            Hide
            shughes Steven Hughes added a comment -

            CCB: FixBy = Someday

            Show
            shughes Steven Hughes added a comment - CCB: FixBy = Someday
            Hide
            dcooley Steve Cooley added a comment -

            I documented the "VectorFormat" field in both the ImpulsiveBurn and FiniteBurn XML. I would think this is all we want documented. SPH: Do you agree? (e.g., I think it would be dangerous to document the IsFiring feature)

            Show
            dcooley Steve Cooley added a comment - I documented the "VectorFormat" field in both the ImpulsiveBurn and FiniteBurn XML. I would think this is all we want documented. SPH: Do you agree? (e.g., I think it would be dangerous to document the IsFiring feature)
            Hide
            shughes Steven Hughes added a comment -

            Steve, Document the deprecation then assign to Darrel P2.

            Show
            shughes Steven Hughes added a comment - Steve, Document the deprecation then assign to Darrel P2.
            Hide
            dcooley Steve Cooley added a comment - - edited

            GMT 3682 assigned to DSC on 4/8/2013. Per SPH direction, opening this new related ticket instead.

            For FuelTank, Thruster, ImpulsiveBurn, and FiniteBurn: All non-numeric fields should not be settable in command mode. (I believe this is working correctly in the code)

            For Spacecraft hardware: SC.Tanks and SC.Thrusters should be settable in command mode. (I believe this is working correctly in the code)

            For DifferentialCorrector, VF13ad, and fminconOptimizer, all fields should not be settable in command mode.(I believe this is working correctly in the code)

            With regard to "hidden" variables:

            (1) From DJC comments in GMT-3682, it appears Thruster has hidden fields, "IsFiring", "C_UNITS", and "K_UNITS". I have never used thses fields since I did not know about them. In discussions with SPH, we think they should not be allowed in command mode.

            (2) From DJC comments in GMT-3682, it appears burn objects have the hidden fields "VectorFormat" and "SpacecraftName." SPH stated that VectorFormat should be allowed in command mode but that "SpacecraftName" should not be. (SPH mentioned that SpacecraftName did not even appear to work).

            I also attach a Word document,Powered Flight and Solver Infrastructure Resource Limitations in Command Mode, which contain my current understanding.

            Show
            dcooley Steve Cooley added a comment - - edited GMT 3682 assigned to DSC on 4/8/2013. Per SPH direction, opening this new related ticket instead. For FuelTank, Thruster, ImpulsiveBurn, and FiniteBurn: All non-numeric fields should not be settable in command mode. (I believe this is working correctly in the code) For Spacecraft hardware: SC.Tanks and SC.Thrusters should be settable in command mode. (I believe this is working correctly in the code) For DifferentialCorrector, VF13ad, and fminconOptimizer, all fields should not be settable in command mode.(I believe this is working correctly in the code) With regard to "hidden" variables: (1) From DJC comments in GMT-3682 , it appears Thruster has hidden fields, "IsFiring", "C_UNITS", and "K_UNITS". I have never used thses fields since I did not know about them. In discussions with SPH, we think they should not be allowed in command mode. (2) From DJC comments in GMT-3682 , it appears burn objects have the hidden fields "VectorFormat" and "SpacecraftName." SPH stated that VectorFormat should be allowed in command mode but that "SpacecraftName" should not be. (SPH mentioned that SpacecraftName did not even appear to work). I also attach a Word document,Powered Flight and Solver Infrastructure Resource Limitations in Command Mode, which contain my current understanding.

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated: