To compile FreeCAD I use this script ... https://github.com/berndhahnebach/FreeC ... Qt5_Py3.sh
your way on debuging seam good to me.
Do you have a github where I can see your code? I might have an idea too where the problem is.
Felt in FEM Workbench
Moderator: bernd
Forum rules
and Helpful information for the FEM forum
and Helpful information for the FEM forum
Re: Felt in FEM Workbench
+1bernd wrote: ↑Wed May 15, 2019 7:03 pm To compile FreeCAD I use this script ... https://github.com/berndhahnebach/FreeC ... Qt5_Py3.sh
That's a well written script.
I have a few doubts:
Code: Select all
sudo apt-get dist-upgrade -y
Also, whats the function of the y flag?
s/seam/seems/
Thanks!
Its here.
Though I haven't committed the latest changes.
I was planning to commit after getting the felt solver to execute properly.
Should I just commit the latest changes and push them?
Re: Felt in FEM Workbench
So I did the investigation and now I know the basics of subprocess.Sudhanshu wrote: ↑Wed May 15, 2019 6:55 pm Investigating that, I got to know about the subprocess library of python which is used in tasks.py.
And it looks really interesting
So now I will explore this, run the solver in python (outside of FreeCAD) and implement that tasks.py.
Also, I was able to run felt solver using python with the following code:
Code: Select all
>>> p = subprocess.Popen(["felt","beam.flt"], cwd="/home/sudhanshu/Documents/Python/", stdout=subprocess.PIPE)
But now I am confused as to what we are doing in the tasks.py
I completely understand this part:
Code: Select all
binary = '/usr/bin/felt' # if something goes wrong the binary path could be set for debugging
if binary is not None:
self._process = subprocess.Popen(
[binary, infile],
cwd=self.directory,
stdout=subprocess.PIPE,
stderr=subprocess.PIPE)
self.signalAbort.add(self._process.terminate)
Code: Select all
output = self._observeSolver(self._process)
Why are we later on deleting "output" without seemingly doing nothing with it?
And I think I better start writing comments for the code, which bring up the question why aren't there much comments in the file of FEM module?
Re: Felt in FEM Workbench
in the regard of the compile script. This runs for me on a vagrant box, means on a clean fresh debian buster, thus I upgrade the box to the latest version.You do not need this. The -y is to overcome the questions ask. "Do you really would like to install?" etc. With -y the script passes by all the questions.
Eventually, start the script, go and get yourself a caffee or a beer, enjoy the beer, come back to your computer aftet a while use fresh compiled FreeCAD
In the regard of comments, yes there should be more in FEM.
Eventually, start the script, go and get yourself a caffee or a beer, enjoy the beer, come back to your computer aftet a while use fresh compiled FreeCAD
In the regard of comments, yes there should be more in FEM.
- hardeeprai
- Posts: 177
- Joined: Sun May 23, 2010 2:41 pm
- Location: Ludhiana, Punjab, India
- Contact:
Re: Felt in FEM Workbench
Though "bernd" has answered. Assuming you to be hacker (on the basis of your approach/discussion/progress in this Forum), mine answer would have been:
Code: Select all
man apt-get
https://fossbytes.com/this-lazy-program ... f-his-job/
--
H.S.Rai
H.S.Rai