the batch job stucked

Wenjun Zhu
Wenjun Zhu Altair Community Member
edited April 2022 in Community Q&A

Hello. I am running Flux on Linux with batch mode.

However, my job stucked. It says "Flux3D (application 2021.2) running", but stuck there.

the batch file and log attached. Could you have a look?

My guess is the license issue. because the same job works well before the license updated last month.

Tagged:

Answers

  • Alexandru-Ionel Constantin
    Alexandru-Ionel Constantin Altair Community Member
    edited April 2022

    Hi Wenjun Zhu,

     

    There is no information about a license issue in the files you attached.

    I think that the issue is related to the geometrybuild.py file, the path, " /home/els20wz/Projects/" where the projects are saved and xlayerslaminationFP.DEX files(lines 1174 and 1144).

    Can you send the log file from /home/els20wz/MyScript/Flux3D_log.py?

     

    Best regards,

    Alexandru

  • Wenjun Zhu
    Wenjun Zhu Altair Community Member
    edited April 2022

    Hi Wenjun Zhu,

     

    There is no information about a license issue in the files you attached.

    I think that the issue is related to the geometrybuild.py file, the path, " /home/els20wz/Projects/" where the projects are saved and xlayerslaminationFP.DEX files(lines 1174 and 1144).

    Can you send the log file from /home/els20wz/MyScript/Flux3D_log.py?

     

    Best regards,

    Alexandru

    Hi, there is only one line in the log. "#! Flux3D 21.2"...

  • Alexandru-Ionel Constantin
    Alexandru-Ionel Constantin Altair Community Member
    edited April 2022

    Hi, there is only one line in the log. "#! Flux3D 21.2"...

    Hi,

    Can you try to remove the pathname " /home/els20wz/Projects/" in the file name at the lines 1144 and 1174 in the geometrybuild.py and try to run it?

    The projects and the xlayerslaminationFP.DEX files will be saved in the same folder as the .py file.

     

  • Wenjun Zhu
    Wenjun Zhu Altair Community Member
    edited April 2022

    Hi Wenjun Zhu,

     

    There is no information about a license issue in the files you attached.

    I think that the issue is related to the geometrybuild.py file, the path, " /home/els20wz/Projects/" where the projects are saved and xlayerslaminationFP.DEX files(lines 1174 and 1144).

    Can you send the log file from /home/els20wz/MyScript/Flux3D_log.py?

     

    Best regards,

    Alexandru

    ok,I will try and get back to you later. thanks!

  • Wenjun Zhu
    Wenjun Zhu Altair Community Member
    edited April 2022

    Hi,

    Can you try to remove the pathname " /home/els20wz/Projects/" in the file name at the lines 1144 and 1174 in the geometrybuild.py and try to run it?

    The projects and the xlayerslaminationFP.DEX files will be saved in the same folder as the .py file.

     

    I tried the very simple one.  the python script is:

    #! Flux3D 21.2
    newProject()
    GeomMeshOptions[1].methodAutomaticMeshVolume=OptimizeMeshGemsActivated(level=OptimizationStandard())
    openModelerContext()
    closeModelerContext()
    lastInstance = PointCoordinates(color=Color['White'],
    visibility=Visibility['VISIBLE'],
    coordSys=CoordSys['XYZ1'],
    uvw=['0',
    '0',
    '1'],
    nature=Nature['STANDARD'])
    saveProjectAs('simpletest.FLU')

     

    Failed. It is running but no project FLU created.

     

    The Flux3D_log.py:

    Loading data model 'Flux_model.stp'
    Recording commands in '/home/els20wz/MyScript/Flux3D_log.py'

    FLUX3D_21.2.0 : 3D Finite Element Electromagnetism
    Dynamic memory + 1024 MiB GUI
    HWU licensing used: /usr/local/packages/apps/altair_flux/2021.2/binary/altair/security/altair_lic.dat
    Build 2108251453 Flux_Release_2021.2 CL69410 Setup CL69446 Lin64 mono-core sharc-node023.shef.ac.uk:3202 els20wz

    14:11:06 11 sec. FLUX3D_21.2.0 kernel initialized

    Flux3D (application 2021.2) running

     

    that's it. running but no results.

     

     

  • SimonGuicheteau
    SimonGuicheteau
    Altair Employee
    edited April 2022

    Hi Wenjun,

    there is already a support request for this question. I suggest we discuss it there and we can share publicly the solution in this forum once we find it.

    Cheers

  • SimonGuicheteau
    SimonGuicheteau
    Altair Employee
    edited April 2022

    It seems the solution was linked with the way Flux was launched in command line in the cluster set up. A lot of information can be found in the API folder of the installation. Especially the folder PBS contains what we use with PBS in order to launch Flux and even configure parametric distribution methods.