Re: [Rugged Users] [Orekit Developers] Building the rugged examples

[MAISONOBE Luc <luc.maisonobe@c-s.fr>]

Hi Andy,

I am adding rugged-users list, as this question is more suited for this list.

Andy Schofield <A.Schofield@sstl.co.uk> a écrit :

> Thanks Luc.
>
> I opted for Eclipse Mars with orekit-7.0 and rugged-1.0 in the end  
> and got the DirectLocation and other examples working OK.
>
> I am interested in whether Orekit is suitable for projecting a  
> single LoS based on an ECEF position, coupled with time, angular  
> offsets between the AOCS frame of reference and the imager frame of  
> reference, attitude of the AOCS FoR and imager characteristics such  
> as FoV.
> Looking at those examples, it seems like the system is geared  
> towards a propagated flight but that the core functionality probably  
> supports what I'm looking at (projection of single image from a  
> mobile phone camera with attitude and GPS value) but wanted to check  
> if the orekit system can support this before I delve too far.

If you never want to compute inverse location (i.e. you never compute
from ground to spacecraft), if you already know the position and los in
Earth frame, and if you don't care about light time correction, abberration
of light and refraction, you can avoid building the full Rugged object and
you can rely on lower level objects. You can directly build an instance of
DuvenhageAlgorithm and call its intersection method, which will only consider
the Digital Elevation Model and a single line of sight.

If you want to let some existing validated code handle frames transforms,
attitude, instrument viewing model, light time correction, abberration of
light correction and refraction, then you should rather build a Rugged  
instance
and call the directLocation(date, position, los) method, only once, with
your single line of sight. It is possible to build the Rugged instance with
an Orekit propagator instead of providing it set of  
position/velocity/attitude,
this may be simpler in your use case.

So you can use Rugged with a single line of sight.

Hope this helps,
Luc

> Regards
> Andy
>
> -----Original Message-----
> From: orekit-developers-request@orekit.org  
> [mailto:orekit-developers-request@orekit.org] On Behalf Of MAISONOBE  
> Luc
> Sent: 04 October 2016 13:15
> To: orekit-developers@orekit.org
> Subject: Re: [Orekit Developers] Building the rugged examples
>
>
> a.schofield@sstl.co.uk a écrit :
>
> > Hi there,
>
> Hi Andy,
>
> > I'm just starting off with the Orekit/Rugged system and wanted to
> > build the 3 examples in the Rugged package i.e. directLocation, DL
> > with DEM and InverseLocation.
> > Using Orekit 8.0 and Rugged 1.0, should these examples still compile?
> > I was just trying the command line javac for now with the following jars...
> > hipparchus-core-1.0.jar;hipparchus-
> > geometry-1.0.jar;orekit-8.0.jar;rugged-1.0.jar
> > on DirectLocation.java (with the import changed from the commons.math3
> > to Hipparchus based on the info in
> > https://www.orekit.org/static/faq.html
>
> Unfortunately, the current released version of Rugged still depends  
> on the previous Orekit (7.x series) and Apache Commons Math.
>
> We plan to do a Rugged release in the next few months so everything  
> is in sync.
>
> For now, you should get the Rugged development version (unreleased  
> but already updated to Orekit 8 and Hipparchus). You can get it  
> directly from the git repository. You can use from the command line  
> something like:
>
>    git clone https://www.orekit.org/git/rugged-main.git
>
> Using any other git tool (eclipse, or any grahical tool), you can  
> adapt the command line above easily.
>
> best regards,
> Luc
>
> > Regards
> > Andy
>
>
>
>
> The information contained in this message is intended for the  
> addressee only and may contain sensitive information. If you are not  
> the addressee, please delete this message and notify the sender; you  
> should not copy or distribute this message or disclose its contents  
> to anyone. Any views or opinions expressed in this message are those  
> of the individual(s) and not necessarily of the organisation. No  
> reliance may be placed on this message without written confirmation  
> from an authorised representative of its contents. No guarantee is  
> implied that this message or any attachment is virus free or has not  
> been intercepted and amended.