shell to shell contact

[UR_]

... compile my branch ...

Just a short question about how to organize all these repos.
ATM, I have two working copies on my harddisk
https://github.com/FreeCAD/FreeCAD.git and https://github.com/UR-0/FreeCAD.git
In near future yours, the third, should be added.
I can't get rid on the feeling that this is a waste of disk space.
Should/could they all live in one working copy, just checking out the appropriated one before compiling.

BTW, I'm on windows using TortoiseGit, strongly avoiding Git bash

[bernd]

BTW, I'm on windows using TortoiseGit, strongly avoiding Git bash

It is up to you if you use git bash or a git GUI ...

Just a short question about how to organize all these repos.
ATM, I have two working copies on my harddisk
https://github.com/FreeCAD/FreeCAD.git and https://github.com/UR-0/FreeCAD.git
In near future yours, the third, should be added.
I can't get rid on the feeling that this is a waste of disk space.
Should/could they all live in one working copy, just checking out the appropriated one before compiling.

They should live in one git repository !!!

Since I do not know how the Gui works I post the bash commands. You need to find the appropriate icon in your gui yourself ...

in your main repository do:

Code: Select all

git remote add bernd https://github.com/berndhahnebach/FreeCAD_bhb  # bernd could be any identifier you give
git fetch bernd  # will download all my branches into your repo
git branch -a  # will show you all available branches including the remote ones
git checkout remotes/bernd/femshellcontact

than you can check with git status or git log -10 --oneline what is checked out and what are the latest commits. It is time to compile. In my main repo I have around 30 or 40 remote repositories included. They are of all the people who contribute code to FEM.

BTW: Git is a beast at beginning. Just do not give up. I promise, If you domesticate the beast you will never give it away, for sure.

[UR_]

added the unit test as well ... compile my branch ... start FreeCAD ... run:

Test failed, because you didn't explicitly set SplitInputWriter

Code: Select all

obj = App.getDocument("Unnamed1").getObject("CalculiXccxTools")
obj.SplitInputWriter=False

to overwrite my preferences.

[bernd]

No I can not set this, because of the unit test ... Unit test on splited file writing would be very difficault ... Thus all examples uses one file. Would you set it in your example or set it to split in the coded example befor writing, just to test if the coded example is ok.

[UR_]

... Unit test on splited file writing would be very difficault ...

I think you got me wrong.
My preferences are usually set to:

Screenshot 003.png (6.54 KiB) Viewed 561 times

Your script has to change this explicitly on CalculiXccxTools object creation to ensure needed settings.

I think unit tests has work despite of different initial user settings.


e.g. line 116 femexamples\contact_shell_shell.py

Code: Select all

        solver_object.SplitInputWriter = False

BTW
line 111:

Code: Select all

        solver_object.GeometricalNonlinearity = "linear"  # really?

Regarding ccx manual, first shot should be done linear
Just to ensure convergence and nonlinear should last significantly longer.
But convergence is ok and setting to nonlinear makes ccx run even faster
Tried with: ccx_2.16_pardiso_dynamic.exe
But output linear looks better

[bernd]

No. I did explicit set this to False to ensure all is in one file! This is done for all coded examples in FEM module code.

Neverless if I do run analysises for myself I use splitted file writing.

[bernd]

BTW
line 111:

Code: Select all

        solver_object.GeometricalNonlinearity = "linear"  # really?

Regarding ccx manual, first shot should be done linear
Just to ensure convergence and nonlinear should last significantly longer.
But convergence is ok and setting to nonlinear makes ccx run even faster
Tried with: ccx_2.16_pardiso_dynamic.exe
But output linear looks better

good to know

[UR_]

This is done for all coded examples in FEM module code.

Sorry, couldn't find appropriate line of code in femexamples\contact_shell_shell.py

[vocx]

Just a short question about how to organize all these repos.
...
BTW, I'm on windows using TortoiseGit, strongly avoiding Git bash

Do not avoid the terminal. If you are going to be a developer, you need to lose fear of the command line.

Follow bernd's advice on setting up the repositories. And do read Source_code_management.

[UR_]

Oops, some more problems with \femexamples\contact_shell_shell.py

Generated shells are inverted.
Red surfaces have to point inward, grey one's outward, otherwise ccx can't interpret mesh correctly.

Screenshot 005.png (17.22 KiB) Viewed 521 times