getdp issueshttps://gitlab.onelab.info/getdp/getdp/-/issues2021-09-15T21:20:21Zhttps://gitlab.onelab.info/getdp/getdp/-/issues/99use getdp for STL. or STEP. files2021-09-15T21:20:21ZJie Liuse getdp for STL. or STEP. filesHallo,
can I use getdp for solving STL or STEP files if they are optimised? Do I need to use the interface to define each physical surface and then set the parameters in getdp?
best wishes
JHallo,
can I use getdp for solving STL or STEP files if they are optimised? Do I need to use the interface to define each physical surface and then set the parameters in getdp?
best wishes
Jhttps://gitlab.onelab.info/getdp/getdp/-/issues/96Symmetry plane for 3D Magnetostatic2021-08-26T09:43:34ZTheo MessinSymmetry plane for 3D MagnetostaticHello,
In order to save computational resources, symmetries can easily be used with getdp (master-slave link).
Considering a 2 stators - 1 rotor axial flux machine, there is a symmetry that can be used: Simulating one stator and half o...Hello,
In order to save computational resources, symmetries can easily be used with getdp (master-slave link).
Considering a 2 stators - 1 rotor axial flux machine, there is a symmetry that can be used: Simulating one stator and half of the rotor should be sufficient. The symmetry plane cuts the rotor in half.
However I have not seen such implementation.
How can such an (anti)symmetric plane be implemented with getdp's A-v formulation?
Best Regards,
Theohttps://gitlab.onelab.info/getdp/getdp/-/issues/93Boolean Union Operation2021-07-30T07:12:23ZMahdi MMTBoolean Union Operationhttps://gitlab.onelab.info/getdp/getdp/-/issues/94getdp .pre file format documentation2021-07-15T12:01:26ZAlexander Shendigetdp .pre file format documentationHello,
I am using getdp for a modal analysis of a motor stator and housing. Currently I have a model with first order tetrahedra and 24385 nodes.
I need a mapping from Node Number (1 .. 24385) and DOF (one of {UX, UY, UZ, ROTX, ROTY, RO...Hello,
I am using getdp for a modal analysis of a motor stator and housing. Currently I have a model with first order tetrahedra and 24385 nodes.
I need a mapping from Node Number (1 .. 24385) and DOF (one of {UX, UY, UZ, ROTX, ROTY, ROTZ}) to DOF number (1 .. 142278). I should be able to generate that mapping from the .pre file, but don't understand the format (Appendix A.2.2 is no big help either). At least the number of all DOF (constrained and non-constrained) is 146310 = 6*24385 = 6*nnodes.
Thank you in advance for your help.https://gitlab.onelab.info/getdp/getdp/-/issues/863D torque computation issue2021-07-15T09:05:03ZTheo Messin3D torque computation issueHello,
I am implementing a 3D model of an axial flux machine with one rotor and two stators.
The example taken as reference is the static formulation in the machine_magstadyn_a.pro .
In the example, the Maxwell tensor is given by:
`T_...Hello,
I am implementing a 3D model of an axial flux machine with one rotor and two stators.
The example taken as reference is the static formulation in the machine_magstadyn_a.pro .
In the example, the Maxwell tensor is given by:
`T_max[] = ( SquDyadicProduct[$1] - SquNorm[$1] * TensorDiag[0.5, 0.5, 0.5] ) / mu0 ;`
This is equivalent to the definition $`\sigma _{ij}={\frac {1}{\mu _{0}}}B_{i}B_{j}-{\frac {1}{2\mu _{0}}}B^{2}\delta _{ij}`$, and seems reusable for the 3D case.
(https://en.wikipedia.org/wiki/Maxwell_stress_tensor)
Then the torque is computed (see comments in code) with the following integral:
$`\int_S (\vec{r} \times (T_{max} \vec{n}) ) / ep`$, with $`ep = |S| / (2\pi r_{avg})`$, where I understand that the `ep` term comes from the fact that the integration happens within the airgap volume (surface in 2D) instead of surface (Line in 2D).
With the folowing code implementation:
`{ Name Torque_Maxwell ; Value { Integral { [ CompZ [ XYZ[] /\ (T_max[{d a}] * XYZ[]) ] * 2*Pi*AxialLength/SurfaceArea[] ] ; In Domain ; Jacobian Vol ; Integration I1; }}}`
The torque is estimated over the rotor air gap and stator air gap surfaces (2D), called by `Print[ Torque_Maxwell[Rotor_Airgap]...` during a PostOperation.
Trying to formulate the torque for the 3D case based on the stress tensor, I come up to the following solution:
`[ CompZ [ XYZ[] /\ (T_max[{d a}] * XYZ[]) ] * 2*Pi / GetVolume[] ]`
The group I pass during the function call is both air discs at the airgap between the rotor and stator.
However the results seem quite wrong. Do you have any suggestion on what to change in this line?
Update -
Giving another try at following the given formula and replacing the surface by the volume, I would write:
`[ CompZ [ XYZ[] /\ (T_max[{d a}] * Unit[Vector[0, 0, Z[]]]) ] * Norm[Vector[X[], Y[], 0]] * 2 * Pi / GetVolume[] ]` which I assume corresponding to $`\int_S (\vec{r} \times (T_{max} \vec{n}) ) / ep`$, with $`ep = |V| / (2\pi r_{avg})`$
or
`[ CompZ [ XYZ[] /\ (T_max[{d a}] * Unit[Vector[0, 0, Z[]]]) ] / HeightDisc ]` which I assume corresponding to $`\int_S (\vec{r} \times (T_{max} \vec{n}) ) / HeightDisc `$, with $`HeightDisc = |V| / |S|`$ As the integration is happening in the (surrounding) volume but the surface integral is required.
Knowing that both air discs are above and below the Z=0 plane, simplifying the normal to `Unit[Vector[0, 0, Z[]]]` ![image](/uploads/ee04bbccb2bb1fcff15b8f3d388887b1/image.png)https://gitlab.onelab.info/getdp/getdp/-/issues/84Machine_magstadyn_a and mastadyn_av_js0_3d derivation of the formulation2021-07-12T08:36:30ZTheo MessinMachine_magstadyn_a and mastadyn_av_js0_3d derivation of the formulationHello,
**Setup:** Working on integrating the Machine_magstadyn_a or mastadyn_av_js0_3d for the simulation of a 3D electric machine.
**Problem:** Difficulty understanding where the formulation comes from
**Questions:**
Are there any ...Hello,
**Setup:** Working on integrating the Machine_magstadyn_a or mastadyn_av_js0_3d for the simulation of a 3D electric machine.
**Problem:** Difficulty understanding where the formulation comes from
**Questions:**
Are there any papers, personal documentation, references or similar that are available or that your could share that would explain the derivation of the 'Formulation' part of the .pro file. (Derivation from the maxwell equations to the Formulation presented in the examples)?
Also, as a mean to validate my assumption: Is the Machine_magstadyn_a formulation re-usable for 3D axial/radial flux machines?
Thanks in advance for your answer,
Theo
Update - the best I have been able to find so far is the following, for those who ask themselves the same questions :)
https://www.sciencedirect.com/science/article/pii/B9780124077096000018 Multiphysics Modeling Numerical Methods and Engineering Applications Elsevier and Tsinghua University Press Computational Mechanics Series 2016, Pages 1-96
and - for simplicity of explaination - https://www.math.uh.edu/\~rohop/Fall_16/downloads/Chapter8.pdfhttps://gitlab.onelab.info/getdp/getdp/-/issues/82Guidance on obtaining stiffness and mass matrices2021-07-10T10:01:46ZAlexander ShendiGuidance on obtaining stiffness and mass matricesDear getdp folks,
I need some guidance on how to obtain the stiffness and mass
matrices for a linear elasticity eigenvalue problem (presumably
as a postprocessing step).
I need to transform them into modal coordinates.
Thanks in adva...Dear getdp folks,
I need some guidance on how to obtain the stiffness and mass
matrices for a linear elasticity eigenvalue problem (presumably
as a postprocessing step).
I need to transform them into modal coordinates.
Thanks in advance!https://gitlab.onelab.info/getdp/getdp/-/issues/87{d a} instead of {curl a} in formulation2021-07-09T07:58:01ZTheo Messin{d a} instead of {curl a} in formulationHello,
Regarding a simple understanding question: Magnetostatic formulation is usually given using the following elements:
`FunctionSpace { {Name Hcurl_a_3D ; Type Form1 ; ... `
`Formulation { Name MagStaDyn_av_js_3D ; Type FemEquati...Hello,
Regarding a simple understanding question: Magnetostatic formulation is usually given using the following elements:
`FunctionSpace { {Name Hcurl_a_3D ; Type Form1 ; ... `
`Formulation { Name MagStaDyn_av_js_3D ; Type FemEquation ; Quantity { { Name a ; Type Local ; NameOfSpace Hcurl_a_3D ; } ...}`
`Equation { Galerkin { [ nu[{d a}] * Dof{d a} , {d a} ] ; In Domain ; Jacobian Vol ; Integration II ; } ...`
May I ask why `b=curl a` is called by `{d a}` instead of `{curl a}` ?
I understand that `{d a}` is the external derivative and is equivalent to `{Grad a}`.
Is it that `a` is not the magnetic vector potential but the scalar potential for the magnetic (vector) field. `b = curl A` holds but the relevant quantity is `b = grad a`?
Thanks!
Update - seems like as `a` is defined as a form1, a curl conform field, `d` is applied and should equivalent to `curl` - to be validated?
![image](/uploads/78339d76cbd2a89d629d758b09a83073/image.png)https://gitlab.onelab.info/getdp/getdp/-/issues/91Could I please have an answer for #822021-07-09T06:38:05ZAlexander ShendiCould I please have an answer for #82Sorry to create a new issue.
I would still like an answer to #82. What is exactly in the *.m and *.bin files? Whom could I please contact by email? Many thanks in advance. Have a great day.Sorry to create a new issue.
I would still like an answer to #82. What is exactly in the *.m and *.bin files? Whom could I please contact by email? Many thanks in advance. Have a great day.https://gitlab.onelab.info/getdp/getdp/-/issues/89Clash between Eigen and GetDP defines2021-06-10T11:56:27ZAnthony RoyerClash between Eigen and GetDP definesThere is a clash between defines in GetDP and Eigen on NIC5 when optimization flags (-march=native) are activated.
Modules:
```
module load releases/2020b
module load foss/2020b
module load CMake/3.18.4-GCCcore-10.2.0
module load Boos...There is a clash between defines in GetDP and Eigen on NIC5 when optimization flags (-march=native) are activated.
Modules:
```
module load releases/2020b
module load foss/2020b
module load CMake/3.18.4-GCCcore-10.2.0
module load Boost/1.74.0-GCC-10.2.0
module load Python/3.8.6-GCCcore-10.2.0
module load Eigen/3.3.8-GCCcore-10.2.0
```
Error:
```
Dans le fichier inclus depuis /home/ulg/ace/ndavi/getdp/Functions/BF_Node.cpp:11:
/home/ulg/ace/ndavi/getdp/contrib/eigen/Eigen/src/Core/arch/AVX/Complex.h: Dans la fonction « void Eigen::internal::ptranspose(Eigen::internal::PacketBlock<Eigen::internal::Packet4cf, 4>&) »:
/home/ulg/ace/ndavi/getdp/Interface/ProData.h:1766:12: erreur: expected unqualified-id before numeric constant
1766 | #define P1 1
| ^
/home/ulg/ace/ndavi/getdp/contrib/eigen/Eigen/src/Core/arch/AVX/Complex.h:405:11: note: dans l'expansion de la macro « P1 »
405 | __m256d P1 = _mm256_castps_pd(kernel.packet[1].v);
|
```Christophe GeuzaineChristophe Geuzainehttps://gitlab.onelab.info/getdp/getdp/-/issues/85Job Failed #565422021-05-28T14:59:06ZNicolas MarsicJob Failed #56542Hi Christophe,
When compiling commit 34671040, the windows64_ci fails to compile: Job [#56542](https://gitlab.onelab.info/getdp/getdp/-/jobs/56542).
There is however no error message (just a few warnings from parts of the code unrelate...Hi Christophe,
When compiling commit 34671040, the windows64_ci fails to compile: Job [#56542](https://gitlab.onelab.info/getdp/getdp/-/jobs/56542).
There is however no error message (just a few warnings from parts of the code unrelated to the commit).
I also tried to rerun the job several times, and it seems to stop every time at a different place...
Any idea about what happens :/?
Could it come from the parallel compilation, which might trigger a fail before printing its stuff on stdout?https://gitlab.onelab.info/getdp/getdp/-/issues/79mpi.h included twice2021-04-18T17:19:01ZAlexander Shendimpi.h included twicempi.h is included twice when using both OpenMPI and PetSC in file Kernel/Operation_Brodcast.cpp.
I "solved" the problem by commenting out the "#include <mpi.h>" statement in Common/GetDPConfig.h (after "#ifdef HAVE_MPI" line.mpi.h is included twice when using both OpenMPI and PetSC in file Kernel/Operation_Brodcast.cpp.
I "solved" the problem by commenting out the "#include <mpi.h>" statement in Common/GetDPConfig.h (after "#ifdef HAVE_MPI" line.https://gitlab.onelab.info/getdp/getdp/-/issues/59g++ 8.2.1 cannot build git/release2021-04-04T17:33:22Zscanfg++ 8.2.1 cannot build git/releaseHello. At:
``[ 12%] Building CXX object CMakeFiles/shared.dir/Functions/BF_Node.cpp.obj``
We fail:
``D:/Download/MinGW-64-souorce/getdp-master/Functions/BF_Node.cpp: In function 'void BF_Node(Element*, int, double, double, double, doubl...Hello. At:
``[ 12%] Building CXX object CMakeFiles/shared.dir/Functions/BF_Node.cpp.obj``
We fail:
``D:/Download/MinGW-64-souorce/getdp-master/Functions/BF_Node.cpp: In function 'void BF_Node(Element*, int, double, double, double, double*)':
D:/Download/MinGW-64-souorce/getdp-master/Functions/BF_Node.cpp:195:41: error: no matching function for call to 'nodalBasis::f(double&, double&, double&, int, double*&) const'
basis->f(u, v, w, NumNode - 1, s);
^
In file included from D:/Download/MinGW-64-souorce/getdp-master/Functions/BF_Node.cpp:17:
D:/MSYS2/mingw64/include/gmsh/nodalBasis.h:39:16: note: candidate: 'virtual void nodalBasis::f(double, double, double, double*) const'
virtual void f(double u, double v, double w, double *sf) const = 0;
^
D:/MSYS2/mingw64/include/gmsh/nodalBasis.h:39:16: note: candidate expects 4 arguments, 5 provided
D:/MSYS2/mingw64/include/gmsh/nodalBasis.h:40:16: note: candidate: 'virtual void nodalBasis::f(const fullMatrix<double>&, fullMatrix<double>&) const'
virtual void f(const fullMatrix<double> &coord,
^
D:/MSYS2/mingw64/include/gmsh/nodalBasis.h:40:16: note: candidate expects 2 arguments, 5 provided
D:/Download/MinGW-64-souorce/getdp-master/Functions/BF_Node.cpp: In function 'void BF_GradNode(Element*, int, double, double, double, double*)':
D:/Download/MinGW-64-souorce/getdp-master/Functions/BF_Node.cpp:439:42: error: no matching function for call to 'nodalBasis::df(double&, double&, double&, int, double*&) const'
basis->df(u, v, w, NumNode - 1, s);
^
In file included from D:/Download/MinGW-64-souorce/getdp-master/Functions/BF_Node.cpp:17:
D:/MSYS2/mingw64/include/gmsh/nodalBasis.h:42:16: note: candidate: 'virtual void nodalBasis::df(double, double, double, double (*)[3]) const'
virtual void df(double u, double v, double w, double grads[][3]) const = 0;
^~
D:/MSYS2/mingw64/include/gmsh/nodalBasis.h:42:16: note: candidate expects 4 arguments, 5 provided
D:/MSYS2/mingw64/include/gmsh/nodalBasis.h:43:16: note: candidate: 'virtual void nodalBasis::df(const fullMatrix<double>&, fullMatrix<double>&) const'
virtual void df(const fullMatrix<double> &coord,
^~
D:/MSYS2/mingw64/include/gmsh/nodalBasis.h:43:16: note: candidate expects 2 arguments, 5 provided
make[2]: *** [CMakeFiles/shared.dir/build.make:479: CMakeFiles/shared.dir/Functions/BF_Node.cpp.obj] Error 1
make[1]: *** [CMakeFiles/Makefile2:841: CMakeFiles/shared.dir/all] Error 2
make: *** [Makefile:163: all] Error 2``
Not sure if this is due to updated overloading rules in g++https://gitlab.onelab.info/getdp/getdp/-/issues/64GetDP tries to call URL http://getdp.info/bin/Windows/getdp-3.2.0-Windows64c....2021-04-04T17:32:38ZHazardousGetDP tries to call URL http://getdp.info/bin/Windows/getdp-3.2.0-Windows64c.zip during executionI am using a simulation application that internally uses GetDP 3.2.0.
Whenever GetDP is called, it tries to access http://getdp.info/bin/Windows/getdp-3.2.0-Windows64c.zip, which gets flagged by our Antivirus solution. If I permit access...I am using a simulation application that internally uses GetDP 3.2.0.
Whenever GetDP is called, it tries to access http://getdp.info/bin/Windows/getdp-3.2.0-Windows64c.zip, which gets flagged by our Antivirus solution. If I permit access, GetDP runs normally. Otherwise it fails to access local files, which leads to erroneous behaviour.
Is there a good reason for this call, what does it do?https://gitlab.onelab.info/getdp/getdp/-/issues/72GetDP running on geometry data created by Gmsh API2021-04-04T08:45:20ZAlbert PiwonskiGetDP running on geometry data created by Gmsh APIHello together,
I implemented a FEM in the Julia PL. I created a mesh by using the Julia Gmsh API.
Now I want to compare my results with a GetDP solution (fixing the example "Magnetodynamics with cohomology conditions" to my problem)....Hello together,
I implemented a FEM in the Julia PL. I created a mesh by using the Julia Gmsh API.
Now I want to compare my results with a GetDP solution (fixing the example "Magnetodynamics with cohomology conditions" to my problem).
Is it necessary to backtranslate the Julia meshing file (.jl) into a Gmsh scripting language file (.geo)?
Or does the GetDP (.pro) file only needs the physical group labels of the generated mesh?
Greeting,
Alberthttps://gitlab.onelab.info/getdp/getdp/-/issues/71Error : You need to compile GetDP with Gmsh support to open2021-01-26T13:24:47ZWANG JIAQIError : You need to compile GetDP with Gmsh support to openWhen I build getDP in ubuntu-18.04, it is well to build it.
However, it fail to run, with error: Error : You need to compile GetDP with Gmsh support to open XXX
root@d98921616f4e://jiaqiwang969/DGFEM-Acoustic/doc/onelab-source/tutoria...When I build getDP in ubuntu-18.04, it is well to build it.
However, it fail to run, with error: Error : You need to compile GetDP with Gmsh support to open XXX
root@d98921616f4e://jiaqiwang969/DGFEM-Acoustic/doc/onelab-source/tutorials/getdp/Electrostatics# getdp microstrip.pro -solve EleSta_v
Info : Running 'getdp microstrip.pro -solve EleSta_v' [GetDP 3.3.1-git-d6d8d43, 1 node, max. 1 thread]
Info : Started (Mon Jan 25 15:37:30 2021, Wall = 0.014082s, CPU = 0.004117s, Mem = 8.97656Mb)
Info : Increasing process stack size (8192 kB < 16 MB)
Info : Loading problem definition 'microstrip.pro'
Info : Selected Resolution 'EleSta_v'
Info : Loading Geometric data 'microstrip.msh'
Error : You need to compile GetDP with Gmsh support to open 'microstrip.msh'https://gitlab.onelab.info/getdp/getdp/-/issues/67Argument dans le mauvais ordre dans la doc de IterativeLoop2020-12-30T19:55:15ZAntoine MarteauArgument dans le mauvais ordre dans la doc de IterativeLoopDans la définition de "IterativeLoop" (section 6.8 Types for Resolution), la liste des arguments fait apparaitre "the relaxation factor" avant "the relative error".
Pourtant, dans les exemple de codes de la doc et de ONELAB, ces deux ar...Dans la définition de "IterativeLoop" (section 6.8 Types for Resolution), la liste des arguments fait apparaitre "the relaxation factor" avant "the relative error".
Pourtant, dans les exemple de codes de la doc et de ONELAB, ces deux arguments sont dans l'ordre inverse (ex 7.9.4 : "IterativeLoop[NL_NbrMax, NL_Eps, NL_Relax]" ).
Il me semble qu'il faut inverser ces deux arguments dans la définition.
J'ai créé un fix, 48dbc2f3, mais je n'ai pas fait de merge request car je ne sais pas trop par quelle branche c'est censé passer ...https://gitlab.onelab.info/getdp/getdp/-/issues/66Something wrong with a periodic constraint2020-11-15T03:12:06ZKotaro MatsuokaSomething wrong with a periodic constraint Hello, maintainers.
I'm now trying to define a periodic constraint in the twisted super conductor wire model.
However, I got error like this.
```
Warning : Node 1854 (-0.0006951479199108561, 8.227617786218665e-05, 0.0004) already exi... Hello, maintainers.
I'm now trying to define a periodic constraint in the twisted super conductor wire model.
However, I got error like this.
```
Warning : Node 1854 (-0.0006951479199108561, 8.227617786218665e-05, 0.0004) already exists with tolerance 2.85657e-11: node 1853 (-0.0006951479199108561, 8.227617786218665e-05, 0.0004)
Warning : Could not find node corresponding to reference node 247 (-0.000683736, 0.000150016, 0.0004)
Error : Constraint Link: bad correspondance of number of Nodes (8054, 8053)
```
This seems to be bug because Node 1853 is at (-0.0006837361169588987 0.0001500164069892594 0.0004).
I attached files to reproduce this message. Just place all files in the same directory and run following commad.
```
sudo docker build -t onelab . && sudo docker run -t onelab
```
This error seems to be generated by `Generate_LinkNodes` but I could not figure out what wrong with this.
I need help. Thank you for any suggestion to find the suspicious piece of code.
[Dockerfile](/uploads/81e89fc1e994e1d5ad4e3622736c42cf/Dockerfile)
[periodic3d.geo](/uploads/9b433cfd6f072792bcd6ddb2023665f2/periodic3d.geo)
[periodic3d.pro](/uploads/c12df4024c060475afa6f8651e298a1d/periodic3d.pro)
[periodic3d_data.pro](/uploads/36891e1584e3ddd2160316814c3ce157/periodic3d_data.pro)https://gitlab.onelab.info/getdp/getdp/-/issues/63Block Low Rank (BLR, MUMPS solver) does not work in the dev-version of GetDP ...2020-09-26T16:55:31ZArtem KhoroshevBlock Low Rank (BLR, MUMPS solver) does not work in the dev-version of GetDP (3.3.1, git-master).In the version 3.3.0 and older, BLR factorization works perfectly when using the MUMPS solver.
In the dev-version (3.3.1, git-master), errors are received immediately when proceeding to factorization:
```
Info : SolveJac[Sys_Mag] ...In the version 3.3.0 and older, BLR factorization works perfectly when using the MUMPS solver.
In the dev-version (3.3.1, git-master), errors are received immediately when proceeding to factorization:
```
Info : SolveJac[Sys_Mag]
Info : N: 5793014 - preonly cholesky mumps
Current memory used: 384 bytes
Maximum memory used: 384 bytes
***Memory allocation failed for SetupCtrl: maxvwgt. Requested size: 18446744039349813256 bytes
*** stack smashing detected ***: terminated
[user:1159904] *** Process received signal ***
[user:1159904] Signal: Aborted (6)
[user:1159904] Signal code: (-186867516)
Segmentation failed
```
To reproduce the error options must be set to:
```
-pc_factor_mat_solver_type mumps
-mat_mumps_icntl_35 1 (or 2 or 3)
```
The error can be reproduced in any model. For example - "Magnets" model from the ONELAB website:
```
Info : Generate[A]
Info : Generate ExtendedGroup '_BF_Entity_14' (GroupsOfNodesOf, None)
Info : Generate ExtendedGroup '_BF_Entity_16' (GroupsOfNodesOf, None)
Info : Solve[A]
Info : N: 5609 - preonly cholesky mumps
Current memory used: 384 bytes
Maximum memory used: 384 bytes
***Memory allocation failed for SetupCtrl: maxvwgt. Requested size: 1125762467889160 bytes
*** stack smashing detected ***: terminated
[user:1161251] *** Process received signal ***
[user:1161251] Signal: Aborted (6)
[user:1161251] Signal code: (213642692)
Segmentation failed
```
In the case of LU-method there are just "segmentation failed" occured.
```
getdp --info
Version : 3.3.1
License : GNU General Public License
Build OS : Linux64
Build date : 20200905
Build host : user-desktop
Build options : 64Bit Arpack[system] Blas Gmsh Gsl Kernel Lapack MPI OpenMP PETSc Python
PETSc version : 3.13.2 (real arithmetic)
Gmsh lib version : 4.6.0 (20200622)
Gmsh lib options : 64Bit ALGLIB Ann Bamg Blas[generic] Blossom Cairo Cgns DIntegration Dlopen DomHex Fltk GMP Gmm Hxt Jpeg Kbipack Lapack[generic] LinuxJoystick MPI MUMPS MathEx Med Mesh Metis Mmg3d Mpeg Netgen ONELAB ONELABMetamodel OpenCASCADE OpenCASCADE-CAF OpenGL OpenMP OptHom PETSc Parser Plugins Png Post QuadTri Solver TetGen/BR Voro++ Zlib
```
PETSc:
`Configure Options: --prefix=/usr/lib/petscdir/3.13.2 --with-openmp=1 --with-hwloc --with-metis --with-parmetis --with-mpi --download-mumps --download-scalapack --download-ptscotch --download-scotch --with-viennacl CFLAGS="-march=native -mtune=native -O3 -pipe" CXXFLAGS="-march=native -mtune=native -O3 -pipe" --with-debugging=0 --with-clanguage=cxx --with-x=0 FOPTFLAGS="-march=native -mtune=native -O3" --force`https://gitlab.onelab.info/getdp/getdp/-/issues/62Allow to override build user2020-08-19T14:01:22ZBernhard M. WiedemannAllow to override build userThis is meant to be a merge-request, but this gitlab would not let me fork because I "reached my project limit" at 0.
You can use `git am` to get this commit:
```diff
From 0c579753b72bec6f5d185bf6d418e5d365f3b86d Mon Sep 17 00:00:00 200...This is meant to be a merge-request, but this gitlab would not let me fork because I "reached my project limit" at 0.
You can use `git am` to get this commit:
```diff
From 0c579753b72bec6f5d185bf6d418e5d365f3b86d Mon Sep 17 00:00:00 2001
From: "Bernhard M. Wiedemann" <bwiedemann@suse.de>
Date: Sat, 8 Aug 2020 13:51:53 +0200
Subject: [PATCH] Allow to override build user
similar to commit 245d5a3c39cf69e9ecb10894addb69daea6ce0e9
See https://reproducible-builds.org/ for why this is good.
This PR was done while working on reproducible builds for openSUSE.
---
CMakeLists.txt | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 5ac523e..68c5295 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -119,10 +119,12 @@ if(NOT GETDP_HOST)
set(GETDP_HOST "${HOSTNAME}")
endif()
-if(NOT PACKAGER)
- set(PACKAGER "unknown")
+if(NOT GETDP_PACKAGER)
+ if(NOT PACKAGER)
+ set(PACKAGER "unknown")
+ endif()
+ set(GETDP_PACKAGER "${PACKAGER}")
endif()
-set(GETDP_PACKAGER "${PACKAGER}")
if(APPLE)
set(GETDP_OS "MacOSX")
--
2.26.2