Reviewing the past archive of test results, this seems to have started happening for the first time on 2019-05-06. There were prior major test system issues before this, but this is the first occurrence I note of the error "Invalid file identifier. Use fopen to generate a valid file identifier" for one of the GroundStation_Iono test cases.
From: gmat-nav <[email protected]> On Behalf Of Cooley, D S. (GSFC-5950) via gmat-nav Sent: Monday, August 12, 2019 3:35 PM To: '[email protected]' <[email protected]>; [email protected]; Shen, Haijun (GSFC-595.0)[OMITRON] <[email protected]> Subject: [gmat-nav] Source of one matlab issue found - but how do we fix it? All, We reviewed my matlab debug script today at the Nav meeting. Thanks to Haijun for suggesting a possible file path issue. The matlab routine diff_gmd_files issues an fopen command using a relative path as given in the example below. ../output/GroundStation_Iono_XSouthYEast_DeepSpace_NoMedia.gmd The GMAT Windows test machine script assumes that the default directory is C:\Users\gsfc580gmattest\Documents\ScriptTest\gmat\bin This is true 97% of the time. For a sample test that failed, the default directory was C:\Program Files\MATLAB\R2019a\bin\win64 So, this is the cause of this issue. How do we fix it? Can we tell test system to go back to default location? For the windows test system in Bldg 11, we could hard-code an absolute path but this is not a good solution for other users with a different directory structure. I don't think the diff_gmd_files routine has access to the default directory location file path. If it did, we could add something like. cd Default_GMAT_Binary_Directory Thoughts? Steve
_______________________________________________ Gmat-buildtest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gmat-buildtest
