jsbsim-devel — JSBSim development issues

Re: [Jsbsim-devel] Helicopter models

[Sean M. <se...@se...>]

Thanks for the R22 links and the Alouette-III link.

In terms of inceptors the plan is to use the following set:

https://www.brunner-innovation.swiss/product/cls-p-cyclic/
https://www.brunner-innovation.swiss/product/cls-p-collective/
https://www.brunner-innovation.swiss/product/cls-p-rudder/

Cheers

-----Original Message-----
From: Ron Jensen <wi...@je...> 
Sent: Friday, April 12, 2019 4:28 PM
To: Development issues <jsb...@li...>
Subject: Re: [Jsbsim-devel] Helicopter models

Or the original archive version: https://github.com/jentron/R22 :)

When I was flying this in flightgear I had actual torque pedals and a collective w/throttle. Not sure how you could fly it with a single joystick...

On Friday 12 April 2019 07:19:56 am Erik Hofman wrote:
> On 4/12/19 11:17 AM, Sean McLeod wrote:
> > Hi
> >
> > I'm looking for some examples of helicopter models in JSBSim. I've 
> > seen the AH1S that's included in the JSBSim source distribution, but 
> > haven't had much luck finding any others online. All the ones I've 
> > found online are based on using Yasim as the FDM.
> >
> > Does anyone have any links to other JSBSim based helicopter models?
>
> There's this model of the Robinson R22 that Ron made once:
> https://github.com/NikolaiVChr/Robinson/tree/master/Aircraft/R22
>
> Erik



_______________________________________________
Jsbsim-devel mailing list
Jsb...@li...
https://lists.sourceforge.net/lists/listinfo/jsbsim-devel
_______________________________________________
The JSBSim Flight Dynamics Model project http://www.JSBSim.org _______________________________________________

Re: [Jsbsim-devel] Problem with nested tests in switches

[Gijs de R. <gij...@ho...>]

Hi Bertrand,

> This should now be fixed in JSBSim and FlightGear.

thanks for the swift fix! My piece of code works fine now.
I'll report any further bugs on the bug tracker, didn't know there was one :-)

Gijs

Re: [Jsbsim-devel] Helicopter models

[Ron J. <wi...@je...>]

Or the original archive version: https://github.com/jentron/R22 :)

When I was flying this in flightgear I had actual torque pedals and a 
collective w/throttle. Not sure how you could fly it with a single 
joystick...

On Friday 12 April 2019 07:19:56 am Erik Hofman wrote:
> On 4/12/19 11:17 AM, Sean McLeod wrote:
> > Hi
> >
> > I’m looking for some examples of helicopter models in JSBSim. I’ve seen
> > the AH1S that’s included in the JSBSim source distribution, but haven’t
> > had much luck finding any others online. All the ones I’ve found online
> > are based on using Yasim as the FDM.
> >
> > Does anyone have any links to other JSBSim based helicopter models?
>
> There's this model of the Robinson R22 that Ron made once:
> https://github.com/NikolaiVChr/Robinson/tree/master/Aircraft/R22
>
> Erik

Re: [Jsbsim-devel] Helicopter models

[Erik H. <er...@eh...>]

On 4/12/19 11:17 AM, Sean McLeod wrote:
> Hi
> 
> I’m looking for some examples of helicopter models in JSBSim. I’ve seen 
> the AH1S that’s included in the JSBSim source distribution, but haven’t 
> had much luck finding any others online. All the ones I’ve found online 
> are based on using Yasim as the FDM.
> 
> Does anyone have any links to other JSBSim based helicopter models?

There's this model of the Robinson R22 that Ron made once:
https://github.com/NikolaiVChr/Robinson/tree/master/Aircraft/R22

Erik


-- 
http://www.adalin.com
High performance synthesizer and virtual reality audio software.

[Jsbsim-devel] Helicopter models

[Sean M. <se...@se...>]

Hi

I'm looking for some examples of helicopter models in JSBSim. I've seen the AH1S that's included in the JSBSim source distribution, but haven't had much luck finding any others online. All the ones I've found online are based on using Yasim as the FDM.

Does anyone have any links to other JSBSim based helicopter models?

Cheers

Re: [Jsbsim-devel] Python Build Failing on Linux

[Ron J. <wi...@je...>]

On Saturday 06 April 2019 10:18:14 am Bertrand Coconnier wrote:
> Hi Ron,
>
>
> Your version of CMake is most likely lower than 3.8 where the generator
> expression $<IF:,> has been introduced.

This is correct, I have 3.7, which is the default in debian Stable.

>
> That's correct. So I have updated the JSBSim code so that the build of the
> Python modules is optional.
> The following command should be hopefully fix your problem (assuming the
> root directory of JSBSim is the parent directory of your build directory
>
> hence the '..' at the end of the command) :
> > cmake -DBUILD_PYTHON_MODULE=OFF ..
>
> Bertrand

This switch works for me, thank you.

Ron

Re: [Jsbsim-devel] Problem with nested tests in switches

[Bertrand C. <bco...@gm...>]

Hi Gijs,

This should now be fixed in JSBSim and FlightGear.

Regards,

Bertrand.

Le dim. 17 mars 2019 à 19:26, Bertrand Coconnier <bco...@gm...> a
écrit :

> Hi Gijs,
>
> I have opened an issue on GitHub
> https://github.com/JSBSim-Team/jsbsim/issues/176 about the problem you
> reported.
>
> Thanks.
>
> Bertrand
>
> Le lun. 11 mars 2019 à 18:12, Gijs de Rooy <gij...@ho...> a
> écrit :
>
>> Hi all,
>>
>> I've got a question about nested tests in switches. The following code
>> does not work as advertised in current FlightGear. Whenever
>> fcs/flaps/cmd-detent-deg == 25 or 30, fcs/flaps/int-cmd-deg is set to
>> 20, even tough the velocity is smaller than 203 (in fact it is 0).
>> Apparently the first nested test ignores the velocity test.
>>
>>         <switch name="fcs/flaps/int-cmd-deg">
>>             <default value="fcs/flaps/cmd-detent-deg"/>
>>             <test logic="AND" value="20">
>>                 velocities/vc-kts GT 203
>>                 <test logic="OR">
>>                     fcs/flaps/cmd-detent-deg == 25
>>                     fcs/flaps/cmd-detent-deg == 30
>>                 </test>
>>             </test>
>>             <test logic="AND" value="25">
>>                 velocities/vc-kts GT 170
>>                 velocities/vc-kts LT 203
>>                 fcs/flaps/cmd-detent-deg == 30
>>             </test>
>>         </switch>
>>
>> The following does work, but it leads to more duplicated code:
>>
>>         <switch name="fcs/flaps/int-cmd-deg">
>>             <default value="fcs/flaps/cmd-detent-deg"/>
>>             <test logic="AND" value="20">
>>                 velocities/vc-kts GT 203
>>                 fcs/flaps/cmd-detent-deg == 25
>>             </test>
>>             <test logic="AND" value="20">
>>                 velocities/vc-kts GT 203
>>                 fcs/flaps/cmd-detent-deg == 30
>>             </test>
>>             <test logic="AND" value="25">
>>                 velocities/vc-kts GT 170
>>                 velocities/vc-kts LT 203
>>                 fcs/flaps/cmd-detent-deg == 30
>>             </test>
>>         </switch>
>>
>> According to an old message by Jon [1], the first one was known to fail
>> back in 2012, but I think it should work nowadays, right? Is it broken
>> (again) or did I miss anything?
>>
>> Thanks!
>>
>> Gijs
>>
>> [1] https://sourceforge.net/p/jsbsim/mailman/message/30022194/
>> _______________________________________________
>> Jsbsim-devel mailing list
>> Jsb...@li...
>> https://lists.sourceforge.net/lists/listinfo/jsbsim-devel
>> _______________________________________________
>> The JSBSim Flight Dynamics Model project
>> http://www.JSBSim.org
>> _______________________________________________
>>
>>

Re: [Jsbsim-devel] Python Build Failing on Linux

[Bertrand C. <bco...@gm...>]

Hi Ron,

Le dim. 31 mars 2019 à 01:37, Ron Jensen <wi...@je...> a écrit :

> I have been unable to build JSBSim for quite some time under linux:
>
> cmake  ../JSBSim-code/
> (...)
> -- Found PythonInterp: /usr/bin/python (found version "2.7.13")
> -- Found Cython: /usr/bin/cython
> -- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found
> version "2.7.13")
> -- Found CxxTest: /usr/include
> -- Found Doxygen: /usr/bin/doxygen (found version "1.8.13")
> -- Found LSB_Release: /usr/bin/lsb_release
> -- Configuring done
> CMake Error at python/CMakeLists.txt:89 (add_custom_command):
>   Error evaluating generator expression:
>
>     $<IF:$<BOOL:>,--config,>
>
>   Expression did not evaluate to a known generator expression
>

Your version of CMake is most likely lower than 3.8 where the generator
expression $<IF:,> has been introduced.


> and then make:
>
> [ 71%] Building Python modules...
> Traceback (most recent call last):
>   File "~/Flight/JSBSim-build/python/setup.py", line 3, in <module>
>     from setuptools import setup
> ImportError: No module named setuptools
> python/CMakeFiles/PythonJSBSim.dir/build.make:62: recipe for
> target 'tests/jsbsim.so' failed
>

That's because the Python module "setuptools" is not installed.


> I have no clue about CMake and Python. How do I fix this? I can live
> without
> the Python modules, but apparently there isn't a switch to turn the python
> module off?
>

That's correct. So I have updated the JSBSim code so that the build of the
Python modules is optional.
The following command should be hopefully fix your problem (assuming the
root directory of JSBSim is the parent directory of your build directory
hence the '..' at the end of the command) :

> cmake -DBUILD_PYTHON_MODULE=OFF ..


>
> Thanks,
>
> Ron
>

Regards,

Bertrand

[Jsbsim-devel] Python Build Failing on Linux

[Ron J. <wi...@je...>]

I have been unable to build JSBSim for quite some time under linux:

cmake  ../JSBSim-code/
(...)
-- Found PythonInterp: /usr/bin/python (found version "2.7.13")
-- Found Cython: /usr/bin/cython
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found 
version "2.7.13")
-- Found CxxTest: /usr/include
-- Found Doxygen: /usr/bin/doxygen (found version "1.8.13")
-- Found LSB_Release: /usr/bin/lsb_release
-- Configuring done
CMake Error at python/CMakeLists.txt:89 (add_custom_command):
  Error evaluating generator expression:

    $<IF:$<BOOL:>,--config,>

  Expression did not evaluate to a known generator expression

and then make:

[ 71%] Building Python modules...
Traceback (most recent call last):
  File "~/Flight/JSBSim-build/python/setup.py", line 3, in <module>
    from setuptools import setup
ImportError: No module named setuptools
python/CMakeFiles/PythonJSBSim.dir/build.make:62: recipe for 
target 'tests/jsbsim.so' failed

I have no clue about CMake and Python. How do I fix this? I can live without 
the Python modules, but apparently there isn't a switch to turn the python 
module off?

Thanks,

Ron

Re: [Jsbsim-devel] Problem with nested tests in switches

[Bertrand C. <bco...@gm...>]

Hi Gijs,

I have opened an issue on GitHub
https://github.com/JSBSim-Team/jsbsim/issues/176 about the problem you
reported.

Thanks.

Bertrand

Le lun. 11 mars 2019 à 18:12, Gijs de Rooy <gij...@ho...> a écrit :

> Hi all,
>
> I've got a question about nested tests in switches. The following code
> does not work as advertised in current FlightGear. Whenever
> fcs/flaps/cmd-detent-deg == 25 or 30, fcs/flaps/int-cmd-deg is set to 20,
> even tough the velocity is smaller than 203 (in fact it is 0). Apparently
> the first nested test ignores the velocity test.
>
>         <switch name="fcs/flaps/int-cmd-deg">
>             <default value="fcs/flaps/cmd-detent-deg"/>
>             <test logic="AND" value="20">
>                 velocities/vc-kts GT 203
>                 <test logic="OR">
>                     fcs/flaps/cmd-detent-deg == 25
>                     fcs/flaps/cmd-detent-deg == 30
>                 </test>
>             </test>
>             <test logic="AND" value="25">
>                 velocities/vc-kts GT 170
>                 velocities/vc-kts LT 203
>                 fcs/flaps/cmd-detent-deg == 30
>             </test>
>         </switch>
>
> The following does work, but it leads to more duplicated code:
>
>         <switch name="fcs/flaps/int-cmd-deg">
>             <default value="fcs/flaps/cmd-detent-deg"/>
>             <test logic="AND" value="20">
>                 velocities/vc-kts GT 203
>                 fcs/flaps/cmd-detent-deg == 25
>             </test>
>             <test logic="AND" value="20">
>                 velocities/vc-kts GT 203
>                 fcs/flaps/cmd-detent-deg == 30
>             </test>
>             <test logic="AND" value="25">
>                 velocities/vc-kts GT 170
>                 velocities/vc-kts LT 203
>                 fcs/flaps/cmd-detent-deg == 30
>             </test>
>         </switch>
>
> According to an old message by Jon [1], the first one was known to fail
> back in 2012, but I think it should work nowadays, right? Is it broken
> (again) or did I miss anything?
>
> Thanks!
>
> Gijs
>
> [1] https://sourceforge.net/p/jsbsim/mailman/message/30022194/
> _______________________________________________
> Jsbsim-devel mailing list
> Jsb...@li...
> https://lists.sourceforge.net/lists/listinfo/jsbsim-devel
> _______________________________________________
> The JSBSim Flight Dynamics Model project
> http://www.JSBSim.org
> _______________________________________________
>
>

[Jsbsim-devel] Problem with nested tests in switches

[Gijs de R. <gij...@ho...>]

Hi all,

I've got a question about nested tests in switches. The following code does not work as advertised in current FlightGear. Whenever fcs/flaps/cmd-detent-deg == 25 or 30, fcs/flaps/int-cmd-deg is set to 20, even tough the velocity is smaller than 203 (in fact it is 0). Apparently the first nested test ignores the velocity test.

        <switch name="fcs/flaps/int-cmd-deg">
            <default value="fcs/flaps/cmd-detent-deg"/>
            <test logic="AND" value="20">
                velocities/vc-kts GT 203
                <test logic="OR">
                    fcs/flaps/cmd-detent-deg == 25
                    fcs/flaps/cmd-detent-deg == 30
                </test>
            </test>
            <test logic="AND" value="25">
                velocities/vc-kts GT 170
                velocities/vc-kts LT 203
                fcs/flaps/cmd-detent-deg == 30
            </test>
        </switch>

The following does work, but it leads to more duplicated code:

        <switch name="fcs/flaps/int-cmd-deg">
            <default value="fcs/flaps/cmd-detent-deg"/>
            <test logic="AND" value="20">
                velocities/vc-kts GT 203
                fcs/flaps/cmd-detent-deg == 25
            </test>
            <test logic="AND" value="20">
                velocities/vc-kts GT 203
                fcs/flaps/cmd-detent-deg == 30
            </test>
            <test logic="AND" value="25">
                velocities/vc-kts GT 170
                velocities/vc-kts LT 203
                fcs/flaps/cmd-detent-deg == 30
            </test>
        </switch>

According to an old message by Jon [1], the first one was known to fail back in 2012, but I think it should work nowadays, right? Is it broken (again) or did I miss anything?

Thanks!

Gijs

[1] https://sourceforge.net/p/jsbsim/mailman/message/30022194/

Re: [Jsbsim-devel] Piston engine

[Simon & J. <sim...@go...>]

Hi Ron, 

My focus is on the practicalities of matching jsbsim piston results with actual known engine performance values.

Initially matching a ordinary aspirated engine in a standard day static test. Then taking the same engine and boosting it with a supercharger or turbo charger and performing the same test.
And finally testing at speed and ensuring that ram effect holds the MP to the tested results.

On 19 January 2019, at 00:59, Ron Jensen <wi...@je...> wrote:

On Friday 18 January 2019 01:50:01 pm Simon Julie Morley via Jsbsim-devel 
wrote:
> Is there anyone willing to work with me and code on the piston engine ?
>
> I’m quite happy to provide the logic, maths  etc...but the C++ is a step
> too far for me.
>
> Regards
>
> Simon

Simon,

I've been lurking for the past few years because I'm working on a Bachelor of 
Science Degree in Applied Mathematics. It just so happens I was discussing 
the JSBSim piston engine model with one of my professors (PhD) this week with 
the idea of documenting it in a mathematical modeling paper.

I'm approaching it with a fresh set of eyes and and newly honed appreciation 
of calculus, ODEs and math modeling skills. What is it you think needs to be 
changed, and why?

Ron


_______________________________________________
Jsbsim-devel mailing list
Jsb...@li...
https://lists.sourceforge.net/lists/listinfo/jsbsim-devel
_______________________________________________
The JSBSim Flight Dynamics Model project
http://www.JSBSim.org
_______________________________________________

Re: [Jsbsim-devel] Piston engine

[Ron J. <wi...@je...>]

On Friday 18 January 2019 01:50:01 pm Simon Julie Morley via Jsbsim-devel 
wrote:
> Is there anyone willing to work with me and code on the piston engine ?
>
> I’m quite happy to provide the logic, maths  etc...but the C++ is a step
> too far for me.
>
> Regards
>
> Simon

Simon,

I've been lurking for the past few years because I'm working on a Bachelor of 
Science Degree in Applied Mathematics. It just so happens I was discussing 
the JSBSim piston engine model with one of my professors (PhD) this week with 
the idea of documenting it in a mathematical modeling paper.

I'm approaching it with a fresh set of eyes and and newly honed appreciation 
of calculus, ODEs and math modeling skills. What is it you think needs to be 
changed, and why?

Ron

[Jsbsim-devel] Piston engine

[Simon J. M. <sim...@go...>]

Is there anyone willing to work with me and code on the piston engine ?

I’m quite happy to provide the logic, maths  etc...but the C++ is a step too far for me.

Regards

Simon

Sent from Mail for Windows 10

Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

[Bertrand C. <bco...@gm...>]

Hi Alan,

It took 3 months overall to figure out how to fix the issues that you
reported !
Now you should get a build with no errors if you pull the last revision of
JSBSim from GitHub.

Let me know if you still find some issues.

Regards,

Bertrand.

Le sam. 10 nov. 2018 à 21:32, Alan Teeder <ajt...@v-...> a écrit :

> Bertrand
>
> Your patch does not quite align with my copy of setup.py.in and therefore
> have not applied it. Here are lines  65-78 :-
>
> # Build & installation process for the JSBSim Python module
> setup(
>     name="${PROJECT_NAME}",
>     version="${PROJECT_VERSION}",
>     cmdclass={'build_ext': QuietBuild, 'install_lib': InstallJSBSimModule},
>     ext_modules=[Extension('jsbsim', ['${JSBSIM_CXX}'],
>                            libraries=['JSBSim'],
>
> include_dirs=[os.path.join('${CMAKE_SOURCE_DIR}',
>                                                       'src'),
>
> os.path.join('${CMAKE_SOURCE_DIR}',
>                                                       'python')],
>
> library_dirs=[os.path.join('${CMAKE_BINARY_DIR}',
>                                                       'src'+config)],
>                            language='c++')])
>
> I have run the RUN_TESTS MSVC project.  It fails on test 5:TestActuator
> and  test 50:FGLOcationTest1.  The relevant sections of  LastTest.Log are
> attached.
>
> Alan
> _______________________________________________
> Jsbsim-devel mailing list
> Jsb...@li...
> https://lists.sourceforge.net/lists/listinfo/jsbsim-devel
> _______________________________________________
> The JSBSim Flight Dynamics Model project
> http://www.JSBSim.org
> _______________________________________________
>
>

Re: [Jsbsim-devel] tools for converting FDM from AVL to JSBSim

[Alan T. <ajt...@v-...>]

From: Magree, Daniel 
Sent: Wednesday, November 7, 2018 2:27 PM
To: jsb...@li... 
Subject: [Jsbsim-devel] tools for converting FDM from AVL to JSBSim

Hi all, I was wondering if you have any advice for converting an FDM generated by AVL (specifically, an AVL xml file generated by Cloud Cap's AVL editor) to something understandable by JSBSim. I could do it by hand or cook something up myself, but I was wondering if you know of any tools out there already.



Daniel





------

Daniel.



Unless someone has written and not published, such a tool I think that you will be out of luck. However this old thread on this list may help https://sourceforge.net/p/jsbsim/mailman/message/23563466/ Looking at the examples on http://rcscratches.com/downloads/crrssim-with-rcs-models/ it seems that the data is not very detailed, so a hand conversion should be simple. Start with a simple generic model generated by JSBSim´s Aeromatic++ program and transfer the data.



My own approach to using graphical aero data is to copy and paste via a spreadsheet. JSBSim supports interpolation within tables. The spreadsheet can be used to manipulate and reformat the AVL data.



Richard Harrison, who posts here from time to time, had done a lot of work using VSPAero and JSBSim.



Alan

Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

[Alan T. <ajt...@v-...>]

Bertrand

Your patch does not quite align with my copy of setup.py.in and therefore have not applied it. Here are lines  65-78 :-

# Build & installation process for the JSBSim Python module
setup(
    name="${PROJECT_NAME}",
    version="${PROJECT_VERSION}",
    cmdclass={'build_ext': QuietBuild, 'install_lib': InstallJSBSimModule},
    ext_modules=[Extension('jsbsim', ['${JSBSIM_CXX}'],
                           libraries=['JSBSim'],
                           include_dirs=[os.path.join('${CMAKE_SOURCE_DIR}',
                                                      'src'),
                                         os.path.join('${CMAKE_SOURCE_DIR}',
                                                      'python')],
                           library_dirs=[os.path.join('${CMAKE_BINARY_DIR}',
                                                      'src'+config)],
                           language='c++')])
I have run the RUN_TESTS MSVC project.  It fails on test 5:TestActuator and  test 50:FGLOcationTest1.  The relevant sections of  LastTest.Log are attached.
Alan

Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

[Bertrand C. <bco...@gm...>]

Le mar. 6 nov. 2018 à 11:32, Alan Teeder <ajt...@v-...> a écrit :

>
>
> *From:* Bertrand Coconnier
> *Sent:* Friday, November 2, 2018 1:15 AM
> *To:* Development issues
> *Subject:* Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017
>
> Le mer. 24 oct. 2018 à 21:04, Alan Teeder <ajt...@v-...> a
> écrit :
>
>>
>>
>> *From:* Bertrand Coconnier
>> *Sent:* Friday, October 19, 2018 3:04 PM
>> *To:* Development issues
>> *Subject:* Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017
>>
>> Hi Alan,
>>
>> Thanks for the feedback.
>>
>> Could you please modify the file python/setup.py.in as described below
>> and restart the build process from scratch (i.e. in a new directory) ?
>>
>> python/setup.py.in
>> @@ -62,7 +62,7 @@ setup(
>>
>> os.path.join('${CMAKE_SOURCE_DIR}',
>>                                                        'python')],
>>
>> library_dirs=[os.path.join('${CMAKE_BINARY_DIR}',
>> -                                                      'src')],
>> +                                                      'src/release')],
>>                             language='c++')])
>>
>> # Build process for the fpectl module (but don't install !!!)
>>
>> Let me know if the compilation succeeds in that case.
>>
>> Regarding the failed tests, could you please re-run them with the command
>> below and investigate if some errors are reported in the file
>> C:/FlightGear/jsbsim/build64/Testing/Temporary/LastTest.log ?
>>
>> > ctest -I 5,45,40
>>
>> Bertrand.
>>
>> -----------------------
>>
>> Betrand
>>
>> It compiles OK now (release build only of course), and I can run the test
>> suite from within the Visual Studio gui.
>>
>> However I do not know how to run the tests using the ctest command. I
>> assume that I have to be in a directory which contains the ctest executable
>> – but do not know where that is.
>>
>> Alan
>>
>
> Hi alan,
>
> I just pushed a commit to JSBSim which should fix the issue you reported.
> Now you should no longer need to modify manually python\setup.py for the
> test suite to build successfully.
>
> Regarding the command ctest -I 5,40,45, it should be launched from C:/FlightGear/jsbsim/build64/.
> The executable ctest.exe is part of the CMake package.
>
> Regards,
>
> Bertrand.
>
> ------------------------------
>
> Bertrand
>
> I have just rebuilt JSBSim with the latest git version, and then ran this
> test
>
> C:\FlightGear\jsbsim\build64> ctest -I 5,40,45
> Test project C:/FlightGear/jsbsim/build64
>     Start 5: TestActuator
> 1/1 Test #5: TestActuator .....................***Failed    0.68 sec
>
> 0% tests passed, 1 tests failed out of 1
>
> Total Test time (real) =   0.72 sec
>
> The following tests FAILED:
>           5 - TestActuator (Failed)
> Errors while running CTest
>
>
> Alan
>

Alan,

Should I understand that you can now build the Python tests without the
manual modification of setup.py.in ?

Regarding the test that fails, you should be able to get more details about
its failure by adding the -V tag to the command line

> ctest -I 5,40,45 -V

Bertrand.

[Jsbsim-devel] tools for converting FDM from AVL to JSBSim

[Magree, D. <Dan...@gt...>]

Hi all, I was wondering if you have any advice for converting an FDM generated by AVL (specifically, an AVL xml file generated by Cloud Cap's AVL editor) to something understandable by JSBSim. I could do it by hand or cook something up myself, but I was wondering if you know of any tools out there already.


Daniel



------

Daniel Magree, Ph.D.

Research Engineer II

Aerospace, Transportation & Advanced Systems Laboratory

Georgia Tech Research Institute

Office: 404.407.6645

www.gtri.gatech.edu

Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

[Alan T. <ajt...@v-...>]

From: Bertrand Coconnier 
Sent: Friday, November 2, 2018 1:15 AM
To: Development issues 
Subject: Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

Le mer. 24 oct. 2018 à 21:04, Alan Teeder <ajt...@v-...> a écrit :



  From: Bertrand Coconnier 
  Sent: Friday, October 19, 2018 3:04 PM
  To: Development issues 
  Subject: Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

  Hi Alan,

  Thanks for the feedback.

  Could you please modify the file python/setup.py.in as described below and restart the build process from scratch (i.e. in a new directory) ?

  python/setup.py.in
  @@ -62,7 +62,7 @@ setup(
                                            os.path.join('${CMAKE_SOURCE_DIR}',
                                                         'python')],
                              library_dirs=[os.path.join('${CMAKE_BINARY_DIR}',
  -                                                      'src')],
  +                                                      'src/release')],
                              language='c++')])
   
  # Build process for the fpectl module (but don't install !!!)


  Let me know if the compilation succeeds in that case.

  Regarding the failed tests, could you please re-run them with the command below and investigate if some errors are reported in the file C:/FlightGear/jsbsim/build64/Testing/Temporary/LastTest.log ?

  > ctest -I 5,45,40

  Bertrand.


  -----------------------

  Betrand

  It compiles OK now (release build only of course), and I can run the test suite from within the Visual Studio gui.

  However I do not know how to run the tests using the ctest command. I assume that I have to be in a directory which contains the ctest executable – but do not know where that is.

  Alan

Hi alan,

I just pushed a commit to JSBSim which should fix the issue you reported. Now you should no longer need to modify manually python\setup.py for the test suite to build successfully.

Regarding the command ctest -I 5,40,45, it should be launched from C:/FlightGear/jsbsim/build64/. The executable ctest.exe is part of the CMake package.

Regards,

Bertrand.



--------------------------------------------------------------------------------

Bertrand 

 

I have just rebuilt JSBSim with the latest git version, and then ran this test 

 

C:\FlightGear\jsbsim\build64> ctest -I 5,40,45
Test project C:/FlightGear/jsbsim/build64
    Start 5: TestActuator
1/1 Test #5: TestActuator .....................***Failed    0.68 sec

0% tests passed, 1 tests failed out of 1

Total Test time (real) =   0.72 sec

The following tests FAILED:
          5 - TestActuator (Failed)
Errors while running CTest


Alan

Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

[Bertrand C. <bco...@gm...>]

Le mer. 24 oct. 2018 à 21:04, Alan Teeder <ajt...@v-...> a écrit :

>
>
> *From:* Bertrand Coconnier
> *Sent:* Friday, October 19, 2018 3:04 PM
> *To:* Development issues
> *Subject:* Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017
>
> Hi Alan,
>
> Thanks for the feedback.
>
> Could you please modify the file python/setup.py.in as described below
> and restart the build process from scratch (i.e. in a new directory) ?
>
> python/setup.py.in
> @@ -62,7 +62,7 @@ setup(
>
> os.path.join('${CMAKE_SOURCE_DIR}',
>                                                        'python')],
>
> library_dirs=[os.path.join('${CMAKE_BINARY_DIR}',
> -                                                      'src')],
> +                                                      'src/release')],
>                             language='c++')])
>
> # Build process for the fpectl module (but don't install !!!)
>
> Let me know if the compilation succeeds in that case.
>
> Regarding the failed tests, could you please re-run them with the command
> below and investigate if some errors are reported in the file
> C:/FlightGear/jsbsim/build64/Testing/Temporary/LastTest.log ?
>
> > ctest -I 5,45,40
>
> Bertrand.
>
> -----------------------
>
> Betrand
>
> It compiles OK now (release build only of course), and I can run the test
> suite from within the Visual Studio gui.
>
> However I do not know how to run the tests using the ctest command. I
> assume that I have to be in a directory which contains the ctest executable
> – but do not know where that is.
>
> Alan
>

Hi alan,

I just pushed a commit to JSBSim which should fix the issue you reported.
Now you should no longer need to modify manually python\setup.py for the
test suite to build successfully.

Regarding the command ctest -I 5,40,45, it should be launched from
C:/FlightGear/jsbsim/build64/.
The executable ctest.exe is part of the CMake package.

Regards,

Bertrand.

Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

[Alan T. <ajt...@v-...>]

From: Bertrand Coconnier 
Sent: Friday, October 19, 2018 3:04 PM
To: Development issues 
Subject: Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

Hi Alan,

Thanks for the feedback.

Could you please modify the file python/setup.py.in as described below and restart the build process from scratch (i.e. in a new directory) ?

python/setup.py.in
@@ -62,7 +62,7 @@ setup(
                                          os.path.join('${CMAKE_SOURCE_DIR}',
                                                       'python')],
                            library_dirs=[os.path.join('${CMAKE_BINARY_DIR}',
-                                                      'src')],
+                                                      'src/release')],
                            language='c++')])
 
# Build process for the fpectl module (but don't install !!!)


Let me know if the compilation succeeds in that case.

Regarding the failed tests, could you please re-run them with the command below and investigate if some errors are reported in the file C:/FlightGear/jsbsim/build64/Testing/Temporary/LastTest.log ?

> ctest -I 5,45,40

Bertrand.


-----------------------

Betrand

It compiles OK now (release build only of course), and I can run the test suite from within the Visual Studio gui.

However I do not know how to run the tests using the ctest command. I assume that I have to be in a directory which contains the ctest executable – but do not know where that is.

Alan

Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

[Bertrand C. <bco...@gm...>]

Hi Alan,

Thanks for the feedback.

Could you please modify the file python/setup.py.in as described below and
restart the build process from scratch (i.e. in a new directory) ?

python/setup.py.in
@@ -62,7 +62,7 @@ setup(

os.path.join('${CMAKE_SOURCE_DIR}',
                                                       'python')],

library_dirs=[os.path.join('${CMAKE_BINARY_DIR}',
-                                                      'src')],
+                                                      'src/release')],
                            language='c++')])

 # Build process for the fpectl module (but don't install !!!)

Let me know if the compilation succeeds in that case.

Regarding the failed tests, could you please re-run them with the command
below and investigate if some errors are reported in the file
C:/FlightGear/jsbsim/build64/Testing/Temporary/LastTest.log ?

> ctest -I 5,45,40

Bertrand.

Le jeu. 18 oct. 2018 à 12:54, Alan Teeder <ajt...@v-...> a écrit :

> I have found the reason for this link error.
>
> I am doing an out of source build in directory
> C:/FlightGear/jsbsim/build64, and
> looking in C:/FlightGear/jsbsim/build64/python/devnull.txt I see this  :-
>
> C:\Program Files (x86)\Microsoft Visual
> Studio\2017\Community\VC\Tools\MSVC\14.15.26726\bin\HostX86\x64\link.exe
> /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO
> /LIBPATH:C:/FlightGear/jsbsim/build64\src /LIBPATH:C:\Python36\libs
> /LIBPATH:C:\Python36\PCbuild\amd64 "/LIBPATH:C:\Program Files
> (x86)\Microsoft Visual
> Studio\2017\Community\VC\Tools\MSVC\14.15.26726\ATLMFC\lib\x64"
> "/LIBPATH:C:\Program Files (x86)\Microsoft Visual
> Studio\2017\Community\VC\Tools\MSVC\14.15.26726\lib\x64"
> "/LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\lib\um\x64"
> "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\ucrt\x64"
> "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\um\x64"
> "/LIBPATH:C:\Program Files (x86)\Microsoft Visual
> Studio\2017\Community\VC\Tools\MSVC\14.15.26726\lib\x64"
> "/LIBPATH:C:\Program Files (x86)\Microsoft Visual
> Studio\2017\Community\VC\Tools\MSVC\14.15.26726\atlmfc\lib\x64"
> "/LIBPATH:C:\Program Files (x86)\Microsoft Visual
> Studio\2017\Community\VC\Auxiliary\VS\lib\x64" "/LIBPATH:C:\Program Files
> (x86)\Windows Kits\10\lib\10.0.17134.0\ucrt\x64" "/LIBPATH:C:\Program Files
> (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\VS\UnitTest\lib"
> "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\um\x64"
> "/LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\lib\um\x64"
> "/LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\Lib\um\x64"
> JSBSim.lib /EXPORT:PyInit_jsbsim
> build\temp.win-amd64-3.6\Release\FlightGear/jsbsim/build64/python/jsbsim.obj
> /OUT:C:/FlightGear/jsbsim/build64/tests\jsbsim.cp36-win_amd64.pyd
> /IMPLIB:build\temp.win-amd64-3.6\Release\FlightGear/jsbsim/build64/python\jsbsim.cp36-win_amd64.lib
> LINK : fatal error LNK1181: cannot open input file 'JSBSim.lib'
>
> If I copy the file C:/FlightGear/jsbsim/build64/src/release JSSim.lib to
> to C:/FlightGear/jsbsim/build64/src , I can then build PythonJSBSim, and
> also run the tests.
>
> All of the tests run, but I get.
> 1>The following tests FAILED:
> 1>      5 - CheckFGBug1503 (Failed)
> 1>     45 - FGLocationTest1 (Failed)
>
> Hope this helps.
>
> Alan
> _______________________________________________
> Jsbsim-devel mailing list
> Jsb...@li...
> https://lists.sourceforge.net/lists/listinfo/jsbsim-devel
> _______________________________________________
> The JSBSim Flight Dynamics Model project
> http://www.JSBSim.org
> _______________________________________________
>
>

Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

[Alan T. <ajt...@v-...>]

I have found the reason for this link error.
I am doing an out of source build in directory C:/FlightGear/jsbsim/build64, and looking in C:/FlightGear/jsbsim/build64/python/devnull.txt I see this  :-
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\bin\HostX86\x64\link.exe /nologo /INCREMENTAL:NO /LTCG /DLL /MANIFEST:EMBED,ID=2 /MANIFESTUAC:NO /LIBPATH:C:/FlightGear/jsbsim/build64\src /LIBPATH:C:\Python36\libs /LIBPATH:C:\Python36\PCbuild\amd64 "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\ATLMFC\lib\x64" "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\lib\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\lib\um\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\ucrt\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\um\x64" "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\lib\x64" "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\atlmfc\lib\x64" "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\VS\lib\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\ucrt\x64" "/LIBPATH:C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Auxiliary\VS\UnitTest\lib" "/LIBPATH:C:\Program Files (x86)\Windows Kits\10\lib\10.0.17134.0\um\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\lib\um\x64" "/LIBPATH:C:\Program Files (x86)\Windows Kits\NETFXSDK\4.6.1\Lib\um\x64" JSBSim.lib /EXPORT:PyInit_jsbsim build\temp.win-amd64-3.6\Release\FlightGear/jsbsim/build64/python/jsbsim.obj /OUT:C:/FlightGear/jsbsim/build64/tests\jsbsim.cp36-win_amd64.pyd /IMPLIB:build\temp.win-amd64-3.6\Release\FlightGear/jsbsim/build64/python\jsbsim.cp36-win_amd64.lib
LINK : fatal error LNK1181: cannot open input file 'JSBSim.lib'

If I copy the file C:/FlightGear/jsbsim/build64/src/release JSSim.lib to  to C:/FlightGear/jsbsim/build64/src , I can then build PythonJSBSim, and also run the tests.

All of the tests run, but I get.
1>The following tests FAILED:
1>      5 - CheckFGBug1503 (Failed)
1>     45 - FGLocationTest1 (Failed)

Hope this helps.

Alan

Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017

[Bertrand C. <bco...@gm...>]

Le dim. 14 oct. 2018 à 12:16, Bertrand Coconnier <bco...@gm...> a
écrit :

> Hi,
>
> I'm quite busy at the moment but I plan to open an issue on GitHub about
> that issue.
>
> Basically, there was 2 distinct issues :
>
> * The humidity feature needs some additional care to handle very high
> altitude flights because, above ~150,000 ft the saturated vapor pressure
> can become higher than the ambient pressure and in that case the humidity
> rate HR can no longer reach 100% or we get negative density.
>

I have filled an issue on GitHub for the bug above.

Bertrand.


>
> * The routine to compute the standard temperature in FGStandardAtmosphere
> was using equations above 360,892 ft that were not accounted for in the
> temperature computations in GetTemperature(). That was causing a drift in
> the temperature bias to keep the ambient temperature constant and equal to
> the value requested by FlightGear (-76.5°C/354°R). At some point, the
> temperature was even becoming negative in Kelvin and Rankine !!!
>
> Bertrand.
>
> Le mer. 10 oct. 2018 à 11:19, Alan Teeder <ajt...@v-...> a
> écrit :
>
>>
>>
>> *From:* Sean McLeod
>> *Sent:* Wednesday, October 10, 2018 9:19 AM
>> *To:* Development issues
>> *Subject:* Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017
>>
>>
>> Hi Alan
>>
>>
>>
>> So what was the fix to get it past 150,000ft?
>>
>>
>>
>> Cheers
>>
>>
>>
>>
>>
>> ------------------
>>
>> Sean
>>
>>
>>
>> Bertrand pushed a fix to flightgear. It does not look as if he pushed
>> them to JSBSim itself.
>>
>>
>>
>> Alan
>>
>