Error in Output about qdyn HOT 32 CLOSED

A quick fix for you would be to go to src/pyqdyn.py and modify line 546 replacing delim_whitespace=True with delimiter=",". Could you check if that fixes the issue?

from qdyn.

Could you provide details of how to reproduce the problem?

from qdyn.

As I extracted the Fort.18 file in excel every value is at its position. But while calling the output file in any one of these wrapper I am not getting any plot. over jupyter as well as in matlab.

from qdyn.

Could you provide details of how to reproduce the problem?

I'm just running your example provided in the manual using Jupyter Notebook.

from qdyn.

Could you provide details of how to reproduce the problem?

I'm just running your example provided in the manual using Jupyter Notebook.

Which example did you try?

from qdyn.

Could you provide details of how to reproduce the problem?

I'm just running your example provided in the manual using Jupyter Notebook.

Which example did you try?

Spring block, RSF, and Singel Asperity

from qdyn.

I've just run the example notebooks, and I cannot reproduce the problem. Are you running the latest version? (2e6646df3b0fbbe4e41dac1b3450b2dbc80c8de4)

from qdyn.

I've just run the example notebooks, and I cannot reproduce the problem. Are you running the latest version? (2e6646df3b0fbbe4e41dac1b3450b2dbc80c8de4)

Yes
I am using (2.2.2).
Is it possible, I may send you a screenshot of the problem over e-mail.

from qdyn.

There have been a few undocumented releases since 2.2.2, so make 100% sure you have compiled the latest commit (git pull origin master and make clean && make in your src directory).

You can attach files (screenshots) by dragging and dropping into the comment box.

from qdyn.

@

from qdyn.

from qdyn.

from qdyn.

This is the issue that I am getting.
there is no problem with p.ox file you can see this in the 2nd screenshot. But p.ot is not giving values.
As I opened the Fort file all the values are at its place.

from qdyn.

Could you revert to commit d9afd684dd5a5269e1f4bfea831faddcab48b46d and check if the problem persists: git checkout d9afd68 && make clean && make in your src directory. Make sure to fully reload the notebooks.

from qdyn.

git checkout d9afd68

Did it but still getting the issue....

from qdyn.

From your screenshots it seems that fort.18 is fine, so that the problem must be in the file reader module. What is your version of Pandas?

from qdyn.

From your screenshots it seems that fort.18 is fine, so that the problem must be in the file reader module. What is your version of Pandas?

Python 3.7.4 (default, Aug 13 2019, 20:35:49)
[GCC 7.3.0] :

from qdyn.

And your Pandas version? import pandas, print(pandas.__version__)

from qdyn.

And your Pandas version? import pandas, print(pandas.__version__)

pandas version 0.25.1

from qdyn.

Hmm, that shouldn't be a problem then. Could you attach your fort.18 to this thread (drag and drop)?

from qdyn.

fort.txt

from qdyn.

Hmm, that shouldn't be a problem then. Could you attach your fort.18 to this thread (drag and drop)?

I attached the fort.txt after changing the extension.

from qdyn.

I'll see if I can have a closer look tomorrow

from qdyn.

I've finally had a chance to look at your fort.18 file. What I noticed, is that yours is comma delimited, while all output should be delimited by white spaces. Any idea why your output is comma delimited?

from qdyn.

I've finally had a chance to look at your fort.18 file. What I noticed, is that yours is comma delimited, while all output should be delimited by white spaces. Any idea why your output is comma delimited?

How would I know I haven't changed anything in the code. I just tried to run the examples only.

from qdyn.

Thank you it worked,
Is it possible to use 3D simulation using python.

from qdyn.

Thank you it worked,

Good to hear that (temporarily) fixes the issue. I'll see if I can figure out why you get comma separated output in the first place.

Is it possible to use 3D simulation using python.

Yes, though 3D simulations have not been tested using the Python wrapper, so you might run into some issues along the way.

from qdyn.

Thank you it worked,

Good to hear that (temporarily) fixes the issue. I'll see if I can figure out why you get comma separated output in the first place.

Is it possible to use 3D simulation using python.

Yes, though 3D simulations have not been tested using the Python wrapper, so you might run into some issues along the way.

Ok, Thank You. I will try, if I will encounter any issues then I will contact you.

from qdyn.

The comma is not a bug but a feature when OCTAVE_OUTPUT is enabled (line 279 of src/output.f90).
You are not using Octave, thus you should set OCTAVE_OUTPUT = .false. in constants.f90, and then recompile the qdyn code (run make).

from qdyn.

That is a good point, I didn't think of that. When you set OCTAVE_OUTPUT = .false., then don't forget to revert back to delim_whitespace=True in pyqdyn.py:546.

Since apparently this behaviour is not caused by a bug in the code, I will now close the issue.

from qdyn.

That is a good point, I didn't think of that. When you set OCTAVE_OUTPUT = .false., then don't forget to revert back to delim_whitespace=True in pyqdyn.py:546.

Since apparently this behaviour is not caused by a bug in the code, I will now close the issue.

well as I checked Constants.f90 the octave output is false.

from qdyn.

from qdyn.