Scilab Home Page | Wiki | Bug Tracker | Forge | Mailing List Archives | Scilab Online Help | File Exchange
ATOMS : CelestLab details
Please login or create an account

CelestLab

CNES Space mechanics toolbox for mission analysis
(3362 downloads for this version - 56006 downloads for all versions)
Details
Version
2.0.1
A more recent valid version with binaries for Scilab 5.2 exists: 2.3.0
Author
CNES - DCT/SB
Owner Organization
CNES - DCT/SB
Maintainers
Alain Lamy
Thierry Martin
Category
License
Creation Date
June 3, 2010
Source created on
Scilab 5.2.x
Binaries available on
Scilab 5.2.x:
Windows 64-bit Windows 32-bit Linux 64-bit Linux 32-bit MacOSX
Install command
--> atomsInstall("celestlab")
Description
            CelestLab is a library of space flight dynamics functions written in Scilab.
This library has been developed and is maintained by CNES (Centre National
d’Etudes Spatiales) for mission analysis purposes. The library is used by CNES
for the trajectory analysis and orbit design of various missions. CelestLab
gathers in ten modules about 200 functions that allow mission designers to
perform various tasks such as: orbit propagation, attitude computation,
elementary manoeuvre computation, change of reference frames, change of
coordinates, three body orbit analysis. CelestLab has been validated against the
CNES flight dynamics reference software. Selected examples from mission analysis
typical studies are provided in the CelestLab help pages.            
Files (2)
[881.97 kB]
Source code archive
Celestlab sources
[2.08 MB]
OS-independent binary for Scilab 5.2.x
Binary version
Automatically generated by the ATOMS compilation chain

News (0)
Comments (4)     Leave a comment 
Comment from Cyrille Tourneur -- June 5, 2010, 10:51:39 AM    
Cannot install the update: I get the following message:

atomsExtract: The extraction of the 
archive 'C:PROGRA~1SCILAB~1.0contribcelestlabcelestlab_2.0.1-3.bin.zip' has failed.

And I can't either switch back to the previous version since the ATOMS package manager 
does not provide the possibility to select package version.

Answer from Pierre Marechal -- June 7, 2010, 08:56:20 AM    
> Cannot install the update: I get the following message:
> 
> atomsExtract: The extraction of the 
> archive 'C:PROGRA~1SCILAB~1.0contribcelestlabcelestlab_2.0.1-3.bin.zip' has failed.


It works for me:

--> atomsInstall celestlab
 ans  =

!celestlab  2.0.1-3  allusers  SCI\contrib\celestlab\2.0.1-3  I  !

Does someone else get this error?

> And I can't either switch back to the previous version since the ATOMS package
> manager does not provide the possibility to select package version.


atomsInstall(['celestlab' '2.0.0'])

Pierre
Answer from Thierry Martin -- June 7, 2010, 09:07:41 AM    
I have tried on my personnal computer (Mandriva 2010) and it works well.
You may install CelestLab using the source code (celestlab-2.0.1-3-src.tar.gz)and
compiling it:
For example, in your scilab.ini

//LOADING AND COMPILING CELESTLAB
DIRBIB="D:\PROGRAM\SCILAB\CELESTLAB\V2.0.1"

try
  exec(DIRBIB+'loader.sce',mode=-1)
catch
  exec(DIRBIB+'builder.sce',mode=-1)
  exec(DIRBIB+'loader.sce',mode=-1)
end

Thierry


> > Cannot install the update: I get the following message:
> > 
> > atomsExtract: The extraction of the 
> > archive 'C:PROGRA~1SCILAB~1.0contribcelestlabcelestlab_2.0.1-3.bin.zip' has failed.
> 
> It works for me:
> 
> --> atomsInstall celestlab
>  ans  =
> 
> !celestlab  2.0.1-3  allusers  SCI\contrib\celestlab\2.0.1-3  I  !
> 
> Does someone else get this error?
> 
> > And I can't either switch back to the previous version since the ATOMS package
> > manager does not provide the possibility to select package version.
> 
> atomsInstall(['celestlab' '2.0.0'])
> 
> Pierre

Answer from Administrator Atoms -- June 7, 2010, 11:31:35 AM    
> Cannot install the update: I get the following message:
> 
> atomsExtract: The extraction of the 
> archive 'C:PROGRA~1SCILAB~1.0contribcelestlabcelestlab_2.0.1-3.bin.zip' has failed.


Which scilab version do you use?

Pierre
Comment from Cyrille Tourneur -- June 9, 2010, 12:36:13 AM    
I have Scilab V5.2.0 installed
When starting scilab, Celestlab is no more present 
However - when running the loader (loader.sce) into scilab - it seems that Celestlab is 
correctly loaded(Celestlab appears in the menu + Celestlab help also available + checked 
some scripts written with former version still OK).
Probably some troubles with the package installer
Thanks 
C. Tourneur

Comment from Cyrille Tourneur -- June 9, 2010, 12:38:39 AM    
More details regarding my install failure below
-->atomsInstall celestlab
atomsExtract: The extraction of the 
archive 'C:PROGRA~1SCILAB~1.0contribcelestlabcelestlab_2.0.1-3.bin.zip' has failed.
 !--error 10000 

at line      51 of function atomsError called by :  
at line      92 of function atomsExtract called by :  
at line     322 of function atomsInstall called by :  
atomsInstall celestlab
Comment from Allan Cornet -- March 25, 2011, 08:24:31 AM    
celestab adds too many variables on stack ...

it should be removed and only used when you need not at startup 

%CL_home                %CL_eqRad          %CL_earthRadius                 %CL_obla 
                  %CL_mu                 %CL_j1jn                   %CL_j2                 
 
%CL_j3 
                  %CL_j4                   %CL_j5                   %CL_j6           
%CL_lightSpeed 
                  %CL_au              %CL_gravCst                %CL_muSun            
%CL_radiusSun 
              %CL_muMoon           %CL_radiusMoon        %CL_obliquity2000            
%CL_rotrEarth 
        %CL_rotrEarthSun                   %CL_g0              %CL_deg2rad              
%CL_rad2deg 
        %CL_criticalInc1         %CL_criticalInc2              %CL_epsilon              
%CL_planetC 
             %CL_TAI_UTC  


Allan
Answer from Allan Cornet -- March 25, 2011, 08:25:57 AM    
> celestab adds too many variables on stack ...
> 
> it should be removed and only used when you need not at startup 
> 
> %CL_home                %CL_eqRad          %CL_earthRadius                 %CL_obla 
>                   %CL_mu                 %CL_j1jn                   %CL_j2              
>     
> %CL_j3 
>                   %CL_j4                   %CL_j5                   %CL_j6           
> %CL_lightSpeed 
>                   %CL_au              %CL_gravCst                %CL_muSun            
> %CL_radiusSun 
>               %CL_muMoon           %CL_radiusMoon        %CL_obliquity2000            
> %CL_rotrEarth 
>         %CL_rotrEarthSun                   %CL_g0              %CL_deg2rad             
> 
> %CL_rad2deg 
>         %CL_criticalInc1         %CL_criticalInc2              %CL_epsilon             
> 
> %CL_planetC 
>              %CL_TAI_UTC  
> 
> 
> Allan



example : %CL_home must be replaced by a function to return path of this module

Allan
Answer from Thierry Martin -- March 25, 2011, 12:03:22 PM    


Could you explain what exactly the problem is. 

(total size of the variables, number of variables ... ? )
Answer from Allan Cornet -- March 25, 2011, 12:47:56 PM    
> 
> 
> Could you explain what exactly the problem is. 
> 
> (total size of the variables, number of variables ... ? )


Yes, and there is no reason to create variables for this

Good pratice here is to define functions

CL_getConstant(...)
CL_getMainPath()


Allan
Answer from Allan Cornet -- March 25, 2011, 03:45:27 PM    
> 
> 
> Could you explain what exactly the problem is. 
> 
> (total size of the variables, number of variables ... ? )


Yes, and there is no reason to create variables for this

Good pratice here is to define functions

CL_getConstant(...)
CL_getMainPath()


Allan
Leave a comment
You must register and log in before leaving a comment.
Email notifications
Send me email when this toolbox has changes, new files or a new release.
You must register and log in before setting up notifications.