-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BR-Wamit #26
Comments
Dear Treppe When saving in .1, .2, ... files, the LEN of the calculation is not saved, so BR imagines itself that it is 1. However, .out files save the LEN dimension.Internally, BR follows the Wamit criteria in chapter 3. For example, for A and B. Are you asking to change the LEN in BR? Best regards |
Dear Iñaki, It is possible export wamit outputs (.1,..2) to the CSV files, for each DOF, using command line? thanks |
Hi Treppe
You can save each plot in .csv or copy the data and paste it anywhere
(excel, ...). However there is not a kind of general 'Save to .csv' option.
The reason is that it is not clear how to arrange that file or set of files
to be useful.
If you have a proposal I may implement it.
Iñaki
…On Mon, 29 May 2023 at 20:07, treppe8k ***@***.***> wrote:
Dear Iñaki,
My mistake was to use BR with outputs wamit runned with ULEN = 2.5.
With ULEN = 1 everything is ok!
------------------------------
It is possible export wamit outputs (.1,..2) to the CSV files using
command line?
[image: csv]
<https://user-images.githubusercontent.com/131455163/241786503-85c32847-0cf9-49e4-83df-c3494ce481f1.png>
thanks
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJGNGJMAVENP7UPLQDOELJ3XITQWLANCNFSM6AAAAAAYSWHTLY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Dear Iñaki, bemrosetta_cl -bem "inputfilepath" -exportToCSV -"Fe-heave" "outputpath" The utility is that csv is universal format and it can be used by any programming language for complex postprocessing |
Hi Treppe
Please indicate clearly if the problem is in the mesh handling or in the
BEM data handling.
If the second, is it opening the .1, .3 files, or the .out file?
Thank you
Iñaki
…On Fri, 2 Jun 2023 at 09:15, treppe8k ***@***.***> wrote:
Dear Inaki
yes, the CSV implementation is perfect... thanks a lot
i have a last point to solve...
in wamit, to run the solver, the gdf used has ulen=2.5. To display the
outputs wamit, BR is configured with ULEN=2.5 but the plots of A, B, Fe are
not displayed correctly. Could you verify it?
with ulen=1 everything is correct.
[image: ulen]
<https://user-images.githubusercontent.com/131455163/242813312-4c8831f2-1637-4ab5-a313-4c9077942764.png>
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJGNGJMGUU3XJJH2FSE4HZ3XJGHK5ANCNFSM6AAAAAAYSWHTLY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
i used bem data handling and this happened with .1 .2 files
thanks |
Hi Treppe
Thank you for the details. Please consider that the .1.2.3... files doesn't
have ULEN, so BEMRosetta considers that it is 1.
However, the .gdf file name is the same than the .1 file name?
If this is the case, when reading a .1, .3, ..., the .gdf file may be read
first just to take the ULEN and the gravity.
Best regards
Iñaki
…On Fri, 2 Jun 2023 at 10:36, treppe8k ***@***.***> wrote:
i used bem data handling and this happened with .1 .2 files
[image: ulen1]
<https://user-images.githubusercontent.com/131455163/242832511-169bdf51-d27d-4c59-b08b-a71e7284cf68.png>
hemisphere R=2.5 , ULEN =2.5 CG 1.25
.1 generated with HO GDF1 (with LID mesh)
buoy01.txt
<https://github.com/BEMRosetta/BEMRosetta/files/11633511/buoy01.txt>
thanks
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJGNGJLYVE766BPSQUHP4TLXJGQYPANCNFSM6AAAAAAYSWHTLY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
dear Iñaki |
Excellent Treppe
Anyway, from now, if the .gdf is with the .1, the ULEN and the gravity are
taken.
Best regards
Iñaki
…On Mon, 5 Jun 2023 at 09:41, treppe8k ***@***.***> wrote:
dear Iñaki
When i use the *.out file everything right
thanks so much by your feedback
—
Reply to this email directly, view it on GitHub
<#26 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJGNGJN55AMKEGA2QYMA7MTXJWEUJANCNFSM6AAAAAAYSWHTLY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Dear Inaki I detected the same issue but this time with pitch RAO results (using .4 and out files)
thanks |
Hi Treppe You are right. This is not implemented in BEMRosetta as I supposed that it was not necessary to scale nondimensional parameters. However, Wamit manual, just before that equation, says 'The non-dimensional definitions of the body motions are'. Thank you! |
It can be found here; https://www.wamit.com/manualv7.4/wamit_v74manualch3.html#x5-210003.3 |
Hi Treppe I have changed how RAO is handled. I hope now it works well with scale. Please check it for me. Iñaki |
Hi Iñaki .4 files ps thanks |
Hi Treppe .4 files does not have the length scale L so BR assigns an 1. Without the .gdf, BR does not know it. Iñaki |
Sorry Treppe, I am a bit lost. If it suits you, we could have a 30 min chat to solve this. Teams or other system is good for me. Best regards |
Dear Iñaki My apologies for long time offline, i am back. I did testings in Excel with WAMIT, HAMS and NEMOH (to compare pitch cylinder truncated coeff. A, B, Fe A meeting would be good, I will send e-mail thanks treppe |
Dear Iñaki,
My geometry is a hemisphere R=2.5 with gravity center =1.25 and ULEN=2.5.
I was testing with ULEN = {1 , 2.5} and something is wrong with the scale
To fix it i had that ...
A= A * (rho/1000) * ulen^PowRad;
B= B * 100
Fe= Fe * (rho/10000) * grav * Aw * ulen^PowDiff;
As usual in the pitch case, PowDiff=3, PowRad=5, Aw=1 , grav=9.81 , rho=1025
Can you review these options in BEMRosetta? The idea is that at least it shows the exported csv as the original data output of wamit
I can transform them using code.
thanks
The text was updated successfully, but these errors were encountered: