You are here: home | CelestLabX | 3.4.2

CelestLabX

CNES Space Mechanics Toolbox for Mission Analysis (extension)

(812 downloads for this version - 57507 downloads for all versions)

Details

Version

3.4.2
A more recent valid version exists: 3.5.0

Author

CNES

Owner Organization

CNES

Maintainer

Alain Lamy

Category

Domain-Specific

License

CeCILL

Creation Date

April 4, 2023

Source created on

Scilab 2023.0.x

Binaries available on

Scilab 2023.0.x:

Linux 64-bit

Windows 64-bit

Install command

--> atomsInstall("celestlabx")

Report a bug

GitLab's issues for celestlabx

Description

                        
******************************************************************************
CelestLabX - CNES Space Mechanics Toolbox for Scilab - Extension Module
Version 3.4.2			     
******************************************************************************

CelestLabX is CelestLab's extension module. 
It contains low level functions that are called by CelestLab. 
Included features are related in particular to STELA (CNES software
for orbit long-term propagation), Two-Line Elements and MSIS2000
atmospheric model. 

Fore more information about CelestLab, see the CelestLab Atoms page 
(http://atoms.scilab.org/toolboxes/celestlab).


Note: 
- CelestLabX can be used with Scilab versions 5.5.x to 2023.x.x 
- The version of CelestLab that should be used is 3.4.2 

Note: binary version has been created using Scilab 6.0.2, but is compatible with
Scilab 2023.0.0.

Files (3)

[7.79 MB]

celestlabx-3.4.2-bin-linux64.tar.gz

Linux 64-bit binary for Scilab 2023.0.x

Binary version for Linux 64 bits (built with Ubuntu 20.04)

Upload date : 2023-04-04 12:16:01
MD5         : c43be8d1f58e5c46dfd5495cf48628a5
SHA1        : 1013b07ebc44f454cdd99d65d8e221bda3a29cd2
Downloads   : 156

[7.75 MB]

celestlabx-3.4.2-bin-win64.zip

Windows 64-bit binary for Scilab 2023.0.x

Binary version for Windows 64 bits

Upload date : 2023-04-04 12:13:24
MD5         : 6a11dec2442867cda9e98362d507e700
SHA1        : 588ca0d63b97461e5727fe942dca2e500936e102
Downloads   : 385

[7.34 MB]

CLx_3.4.2.zip

Source code archive

Upload date : 2023-04-04 12:05:46
MD5         : 7ecc531492a471003d32e0d4acdc79c0
SHA1        : 259692e70babadff64a3bd3d5b7f930d13879853
Downloads   : 271

News (0)

Comments (4) ↑ Leave a comment

Comment from Hani Ibrahim -- April 4, 2023, 09:21:55 PM

Error building CelestlabX 3.4.2 on macOS 13.3 Ventura with Scilab 2023.0.0

Independently if you build the toolbox
a) automatically via Atoms GUI or
b) manually via sources with builder.sce

CelestlabX will build properly w/o any errors. But after restarting Scilab or running
loader.sce I get the same error: 'error on line #19: "*** CelestLabX: Error in
log initialization"'

Output after Atoms build and restart: 
Start CelestLabX
	Load macros
	Load gateways
	Load configuration
	Load Java packages
	Load STELA => Invalid STELA path:
/Users/[xx]/scilab-2023.0.0.app/Contents/share/scilab/contrib/celestlabx/3.4.2/thirdparty/stela
	Check directory validity and/or STELA version
atomsLoad: An error occurred while loading 'celestlabx-3.4.2': (<- translated
to English)
	exec: error on line #19: "*** CelestLabX: Error in log initialization"

Via manual build running cleaner.sce displays (translated from German):
at line 59 of executed file /Users/[xx]/Downloads/celestlabx/cleaner.sce
perform_clean: error on line #17: "exec: Cannot open file cleaner.sce."

Comment from Alain Lamy

-- April 5, 2023, 07:13:37 AM

Hello, 

I would have to look at what happened in more detail, but the solution in this case is
probably to delete the file named "celestlabx_config.txt" in the
"SCIHOME" directory and start Scilab again (and load the toolboxes).

Comment from Hani Ibrahim -- April 5, 2023, 06:50:55 PM

Thank you for your prompt response, Alain.

That was the problem. I built the toolbox outside from /Applications and than copied the
app-bundle to the Application folder after. A uninstall and rebuild in the Applications
folder does not work because of celestlabx_config.txt. conf.STELA_ROOT is not specified as
a relative but as an absolute path in this file. And after moving the bundle the path does
not match anymore of course.

Thanks a lot. Problem solved.

Comment from Alain Lamy

-- February 7, 2024, 10:38:09 AM

For information, some changes have been made in the next version (3.5.0) regarding this 
point that should avoid this problem to happen again. 
 
Alain