-
Notifications
You must be signed in to change notification settings - Fork 28
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
BUG: TableExportConfigManager Updated but not used when exporting #313
Comments
This morning i had another idea it to just overwrite the Again when running
The output file shows something that is did not select (see first post) |
Hi @gvandewiel86, |
Hi @OndraMichal, are you referring to the options that i need to manually set when using the GUI (e.g. selecting load combinations, etc) or selecting the correct "export profile". As we are currently performing a manual export every time we ran the calculations, i would be happy to have a (hacky) work-around or to modify the default "export profile" and export results for all load cases and combinations. Howwever it seems to not respect the settings in the default profile (made in the GUI) so am i correct to assume that it uses some "hard coded" export setting which is not controllable by the user in any way? |
Hi, |
Hi, is there any news on this bug? And where can i keep track of this bug? I could not find the bug number in the Dlubal extranet website or here on Github? |
Hey @gvandewiel86, the bug #163283 is converted to ToDo #15402 and it will be completed as soon as possible. Thank you for your patience. |
Describe the bug
After a lot of experiments and testing i finally got the TableExportConfigManager working and have added a second (id=2) setup which should only export the
Member Internal Forces by Section
. It is set as the default config, however when i run the theExportResultTablesWithDetaliedMembersResultsToXML
function as provided by the RFEM Client it does not honor the settings.As far as i can both in SOAP as in the Python files there is no option to force the use of Config with id=2.
To Reproduce
Expected behavior
I am aware that the requested results are part of the output file, however in the case we are looking at we will be exporting a large model (~2000 members) and approximately 400 load combinations resulting in 800-900 MB file when exporting directly from RFEM.
With all the additional output the will grow to huge sizes which is to be parsed externally.
i would expect that the default config is followed by Webservices as is when exporting the tables using RFEM.
If this is not the case i would expect to see an option the forcibly select an export config.
Expected results
Actual Results
A clear and concise description of what you expected to happen.
Screenshots
Desktop (please complete the following information):
Additional context
Your soonest reply is highly appreciated as our project is currently on hold awaiting your response.
The text was updated successfully, but these errors were encountered: