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

After adding a hardware with the spacecraft such as fuel tanks, then the user can only ask for fuel mass left in the attached tank(s) through script and not via the GUI.

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: P1
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: R2013a
    • Component/s: Report Files (FRR-30)
    • Labels:
      None
    • Environment:

      Windows 7 Enterprise 64-bit

      Description

      If the user adds any hardware with the spacecraft such as fuel tanks, then the user can only ask for fuel mass left in the attached tank(s) through script and not via the GUI. In ReportFile window and in the 'ParameterSelectDialoge' window, no GUI icon for hardware shows up and there is no way to add fuel mass left in the attached tank(s) via GUI.

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            rqureshi Rizwan Qureshi added a comment -

            Hi Linda,

            I added a script for this bug. This will make it easier for you to see this behavior that i have described in the Description section. Thanks!

            Show
            rqureshi Rizwan Qureshi added a comment - Hi Linda, I added a script for this bug. This will make it easier for you to see this behavior that i have described in the Description section. Thanks!
            Hide
            rqureshi Rizwan Qureshi added a comment -

            Hello Linda,

            I talked with Steve Hughes about this particular issue and he raised a very good point. He mentioned that this issue is not necessarily a bug. Its just that the option of adding tank fuel mass is missing in the GUI world. Before you begin to work on this issue, could you please tell me that approximately how long would it take for you to fix this issue?

            If this issue takes you more than 5-6 hours to resolve, then we should not work on this issue. Rather as Steve Hughes and I discussed that it is OK for us to not have this GUI capability as we cannot translate every single capability that we have in script world into the GUI world.

            So solution to this issue would be that I would simply mention in the FRR-30 Spec document that reporting fuel mass is not available via GUI and that the user must use the script in order to access fuel mass variable. This is a quick fix solution to this, as oppose to you spending your valuable time in fixing this issue, especially if this issue will take you more than 5-6 hours to resolve.

            Please let me know. Thanks!

            Show
            rqureshi Rizwan Qureshi added a comment - Hello Linda, I talked with Steve Hughes about this particular issue and he raised a very good point. He mentioned that this issue is not necessarily a bug. Its just that the option of adding tank fuel mass is missing in the GUI world. Before you begin to work on this issue, could you please tell me that approximately how long would it take for you to fix this issue? If this issue takes you more than 5-6 hours to resolve, then we should not work on this issue. Rather as Steve Hughes and I discussed that it is OK for us to not have this GUI capability as we cannot translate every single capability that we have in script world into the GUI world. So solution to this issue would be that I would simply mention in the FRR-30 Spec document that reporting fuel mass is not available via GUI and that the user must use the script in order to access fuel mass variable. This is a quick fix solution to this, as oppose to you spending your valuable time in fixing this issue, especially if this issue will take you more than 5-6 hours to resolve. Please let me know. Thanks!
            Hide
            gmatloj Linda Jun added a comment -

            My estimate for adding this new feature will be about 7-8 hours. I need to work on the ParameterSelectDialog anyway to fix whole array or array element selection for ReportFile and Report command. So I was planning on adding hardware Parameter selection while I'm working on that dialog.

            Show
            gmatloj Linda Jun added a comment - My estimate for adding this new feature will be about 7-8 hours. I need to work on the ParameterSelectDialog anyway to fix whole array or array element selection for ReportFile and Report command. So I was planning on adding hardware Parameter selection while I'm working on that dialog.
            Hide
            rqureshi Rizwan Qureshi added a comment -

            sounds good then. So we should fix this issue then. Yes you can go ahead and work on this bug whenever you plan to! Thanks for the input.

            Show
            rqureshi Rizwan Qureshi added a comment - sounds good then. So we should fix this issue then. Yes you can go ahead and work on this bug whenever you plan to! Thanks for the input.
            Hide
            gmatloj Linda Jun added a comment -

            Fix should be in 2012-06-13 build or later.

            Note: The total time spent includes Code QA for ParameterSelectDialog (3h) and GuiItemManager (3h).

            Show
            gmatloj Linda Jun added a comment - Fix should be in 2012-06-13 build or later. Note: The total time spent includes Code QA for ParameterSelectDialog (3h) and GuiItemManager (3h).
            Hide
            rqureshi Rizwan Qureshi added a comment -

            Verified the fixture. Works fine!

            Show
            rqureshi Rizwan Qureshi added a comment - Verified the fixture. Works fine!
            Hide
            rqureshi Rizwan Qureshi added a comment -

            Closing this bug after verification. ReportFile specs doc is done.

            Show
            rqureshi Rizwan Qureshi added a comment - Closing this bug after verification. ReportFile specs doc is done.

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 3 days, 4 hours
                  3d 4h