I don’t disagree with you. I’ll think about it more. My brain is preoccupied at the moment.

 

Jon

 

 

From: Bill Galbraith [mailto:billg42@bellsouth.net]
Sent: Saturday, November 27, 2010 7:11 PM
To: 'Development issues'
Subject: Re: [Jsbsim-devel] JSBSim Script Tutorial 1 - Released

 

I put the script files in /aircraft/Tutorial_1/scripts. What I was attempting to do is structure it so that the JSBSim directory could contain multiple sets of aircraft and tests. What happens when JSBSim is more fully populated, and I have the same test for several different aircraft? Am I stuck with the name Tutorial_1_2c2_a.xml for a test name in the /scripts directory?  I don't see why the scripts couldn't reside under the aircraft directory, if that were desirable for a particular aircraft. especially when there could be dozens of tests. The other aircraft don't have many scripts. I see 7 scripts for the C172, but are they all for the same model, and which model?  (No, 6 for c172x, 1 for c172r).

 

The current code supports placing the scripts under the aircraft directory, so it's just an organizational issue. By putting my test scripts under the aircraft/Tutorial directory, you certainly know that they go together.  When I want to run the same tests on another aircraft, but with slightly different initial conditions or control inputs, I just have to copy that scripts/ directory over, and off I go, without having to rename dozens of files.

 

I put the scripts and the initialization files in the same directory, which is under the aircraft (aircraft/Tutorial_1/scripts in my case). I was constrained with the initialization files. I would have prefered to NOT have the initialization file at all, but embed that information in the test file. That way, I have all the information for a test in one file. A quick check of a recent FAA certified sim shows 123 test scripts. It is simpler to have all the information contained in one file, instead of two files, especially if those files are in different directories. What if I were working under someone else's Configuration Control System, and had to change the headers in all the files. 123 files or 246 files?  Been there, done that. I guess I could have had a default initialization, and then in the individual script files reset it to the test conditions before trimming. That would have be a little confusing specifying a trim condition n one place, then overwritting in in another.

 

I guess I was trying to present, by example, an alternative to organization, one that might be a little more robust if these models are taken deeper, which I have done with this Tutorial_1 aircraft. What I was hoping is that maybe students that are using Datcom+ and JSBSim could write tests for their aircraft, and maybe contribute them back to the group, so that eventually, we have more tests for more aircraft, so that each new guy isn't reinventing the wheel, but maybe pushing the wheel a little further up the hill.

 

Bill 

 

 

 

 

 

 


From: Jon S. Berndt [mailto:jonsberndt@comcast.net]
Sent: Saturday, November 27, 2010 5:07 PM
To: 'Development issues'
Subject: Re: [Jsbsim-devel] JSBSim Script Tutorial 1 - Released

I got a chance to look at this package today. Comments:

 

Scripts should go in the scripts/ directory under the main JSBSim release directory. The aircraft config file should go under a subdirectory of aircraft/, with the same name as the aircraft, minus the .xml extension. Initialization files should also go in the aircraft config file directory.

 

I’ll have some more on the plotting scripts later.

 

Jon

 

 

From: Bill Galbraith [mailto:billg42@bellsouth.net]
Sent: Wednesday, November 24, 2010 1:03 PM
To: 'Development issues'
Subject: [Jsbsim-devel] JSBSim Script Tutorial 1 - Released

 

Okay, since there were no other comments, I'll go ahead and release this package.

 

www.holycows.net/JSBSim_Script_Tutorial.pdf

www.holycows.net/JSBSim_Script_Tutorial_1.zip

 

Someone please incorporate the model into CVS. Jon will figure out where to put the Tutorial PDF file, either in that directory, or elsewhere with other documentation.

 

Happy Thanksgiving to all, and to all a get week off. Anyone going to I/ITSEC in Orlando next week?  PM me if you are, and want suggestions on fine dining or other local tips.

 

Bill