Atom topic feed | site map | contact | login | Protection des données personnelles | Powered by FluxBB | réalisation artaban
You are not logged in.
Hello,
how can I get root access in salome sif container system for example to edit asrun? What is the default keyword?
Greeting
The superfluous chase, is to miss the essential.
Jules Saliège
Offline
hello
why not building a sand box from the container
you then have full access to everything as regular user
once this done astk and as_run seem to open much faster
on the other hand i am very curious to know what you would edit in as_run
jean pierre aubry
consider reading my book
freely available here https://framabook.org/beginning-with-code_aster/
Offline
Hello Mr. Aubry,
"a sand box from the container" Is this for a conventional people possible?
In asrun I want edit first $tmp to our NFS System outside sif container.
But my favorite way to get Code-Aster 15.5 which looks like in good old day's before 2020. A setup.py in a Debian or Ubuntu System, no sif, not other way's..
Greeting Markus
Last edited by m_golbs (2023-02-02 16:20:55)
The superfluous chase, is to miss the essential.
Jules Saliège
Offline
it is possible
i did it that way and it worked
singularity build --sandbox your_container_sandbox your_container.sif
singularity exec [options] your_container_sandbox
according to instrutions found here
https: [double slash 3w] .nas.nasa.gov/hecc/support/kb/best-practices-for-running-singularity-on-nas-systems_659.html
cant this tmp change be specified in the .export file ?
consider reading my book
freely available here https://framabook.org/beginning-with-code_aster/
Offline
Hello Mr. Aubry,
many thanks! But the old way to compile a code-aster from source is also possible? I don't need the salome system in the same "container".
"cant this tmp change be specified in the .export file ?" I think, yes. But I like basic asrun configurations.
Greeting Markus
The superfluous chase, is to miss the essential.
Jules Saliège
Offline
But the old way to compile a code-aster from source is also possible?.
i dot not think this is possible
I don't need the salome system in the same "container".
neither do i!!
this all salome-meca containerized way of doing things is
a pain in the neck
i struggle more with that than with an old style way
consider reading my book
freely available here https://framabook.org/beginning-with-code_aster/
Offline
Hello Mr. Aubry,
I want solve numerical problems, but this time (since 2021) I work for more then 99% of the time on container, systems,.., and so on. It is a great catastrophe! In 2009 I start with Code-Aster. To 2020 was Code-Aster a good FEM System for me. I think, I will bury Code-Aster use after 14 years next days. The last chance that I have is our HPC specialist. He compile Code-Aster 15.05 for our HPC system. I will ask him, if it possible to compile a 15.05 for my Debian or Ubuntu wortkstation.
Greeting Markus
The superfluous chase, is to miss the essential.
Jules Saliège
Offline
The last chance that I have is our HPC specialist. He compile Code-Aster 15.05 for our HPC system. I will ask him, if it possible to compile a 15.05 for my Debian or Ubuntu wortkstation.
i suppose you mean version 15.5
whatever it is if you found out a way to build a stand alone version of code_aster the old way (not in a container) i had like to know it
consider reading my book
freely available here https://framabook.org/beginning-with-code_aster/
Offline
Hello Mr. Aubry,
that is a little bit difficult.
║ La base GLOBALE a été constituée avec la version 15.05.00 ║
║ et vous utilisez la version 15.06.00
Here the listings:
HPC Output:
<INFO> Demarrage de l'execution.
-- CODE_ASTER -- VERSION : EXPLOITATION (stable) --
-- CODE_ASTER -- VERSION : EXPLOITATION (stable) --
Version 15.5.0 modifiee le 13/05/2022
revision c610c51d7174 - branche 'v15'
Version 15.5.0 modifiee le 13/05/2022
revision c610c51d7174 - branche 'v15'
Copyright EDF R&D 1991 - 2023
Execution du : Tue Jan 3 15:23:25 2023
Nom de la machine : beo-01
Architecture : 64bit
Type de processeur : x86_64
Systeme d'exploitation : Linux-5.4.180-ql-generic-12.0-14-x86_64-with-glibc2.29
Langue des messages : en (UTF-8)
Version de Python : 3.8.10
Version de NumPy : 1.17.4
Copyright EDF R&D 1991 - 2023
Execution du : Tue Jan 3 15:23:25 2023
Nom de la machine : beo-01
Architecture : 64bit
Type de processeur : x86_64
Systeme d'exploitation : Linux-5.4.180-ql-generic-12.0-14-x86_64-with-glibc2.29
Langue des messages : en (UTF-8)
Version de Python : 3.8.10
Version de NumPy : 1.17.4
Parallelisme MPI : actif
Rang du processeur courant : 1
Nombre de processeurs utilises : 8
Parallelisme MPI : actif
Rang du processeur courant : 0
Nombre de processeurs utilises : 8
Parallelisme OpenMP : actif
Nombre de processus utilises : 1
Parallelisme OpenMP : actif
Nombre de processus utilises : 1
Version de la librairie HDF5 : 1.10.5
Version de la librairie HDF5 : 1.10.5
Version de la librairie MED : 4.1.0
Version de la librairie MED : 4.1.0
Librairie MFront : non disponible
Librairie MFront : non disponible
Version de la librairie MUMPS : 5.2.1
Version de la librairie MUMPS : 5.2.1
Librairie PETSc : non disponible
Librairie PETSc : non disponible
Version de la librairie SCOTCH : 6.0.10
Version de la librairie SCOTCH : 6.0.10
SIF Workstation Salome version output:
╔════════════════════════════════════════════════════════════════════════════════════════════════╗
║ <A> <JEVEUX_08> ║
║ ║
║ La base GLOBALE a été constituée avec la version 15.05.00 ║
║ et vous utilisez la version 15.06.00 ║
║ ║
║ Conseil : ║
║ En général, la base ne peut-être utilisée qu'avec la version du code l'ayant construite, ║
║ les catalogues d'éléments sont stockés dans la base lors de sa création, or certaines ║
║ structures de ║
║ données s'appuient sur leur description qui peut varier d'une version à l'autre. ║
║ ║
║ ║
║ Ceci est une alarme. Si vous ne comprenez pas le sens de cette ║
║ alarme, vous pouvez obtenir des résultats inattendus ! ║
╚════════════════════════════════════════════════════════════════════════════════════════════════╝
Greeting Markus
Last edited by m_golbs (2023-02-13 11:54:09)
The superfluous chase, is to miss the essential.
Jules Saliège
Offline
i do not really understand what is your question
but the message looks like you are trying to open with a version of code aster (15.6) a bas that was created with a previous version (15.5)
this is not allowed
consider reading my book
freely available here https://framabook.org/beginning-with-code_aster/
Offline
Hello,
"(15.6) a bas that was created with a previous version (15.5) this is not allowed" I skilled. "15.05.00 and 15.06.00 only notations"
The basic question are the root access to the salome_meca_xxxx.sif. But I will to bury sif container.
I will get probably a nativ Code-Aster version 15.5 for Ubuntu 20.04 LTS, an install script and deb files, from our HPC specialist. So I can install simple Code-Aster on every 20.04 LTS Workstation, no more sif... Its so simple how in old days... When this works, every can use this...
Greeting Markus
2023-02-15 from our HPC specialist receive:
aster-15.5-opse-openmpi-gcc-4.0-bin_15.5.0-ql.1+12-focal_amd64.deb
astk-common-2021-opse_2021.0-ql.1+12-focal_amd64.deb
codeaster-run-2021-opse_2021.0-ql.1+12-focal_amd64.deb
libhdf5-1.10-opse-openmpi-gcc-4.0_1.10.5-ql.3+12-focal_amd64.deb
libmed-4.1-opse-openmpi-gcc-4.0_4.1.0-ql.1+12-focal_amd64.deb
libmetis-5.1-opse-gcc_5.1.0-ql.5+12-focal_amd64.deb
libparmetis-4.0-opse-openmpi-gcc-4.0_4.0.3-ql.6+12-focal_amd64.deb
libptscotch-6.0-opse-openmpi-gcc-4.0_6.0.10-ql.1+12-focal_amd64.deb
libscalapack-2.2-opse-openmpi-gcc-4.0_2.2.0-ql.1+12-focal_amd64.deb
libscotch-6.0-opse-gcc_6.0.10-ql.1+12-focal_amd64.deb
I will test this...
Hello,
our HPC specialist has managed (I didn't have time to test, that's why it took so long) to build a Code-Aster 15.5 version natively without containers. It is Code-Aster MPI without sif and without Salome & Co. It now runs on a normal Ubuntu 20.04 workstation version. Only package sources have to be included and the 20MB Code-Aster binary files have to be loaded.
Greetings Markus
Last edited by m_golbs (2023-05-03 15:53:13)
The superfluous chase, is to miss the essential.
Jules Saliège
Offline