- Welcome to GeoDict Forum.
Recent posts
#91
Basic functionality and features / Re: Error message when trying ...
Last post by djauffres - June 15, 2023, 02:56:25 PMThank you for your suggestion, using virtualGL actually solved the issue.
#92
Basic functionality and features / Re: Error message when trying ...
Last post by Aaron Widera - June 14, 2023, 04:16:17 PMHello,
nice to have you here as a new user.I assume you start GeoDict from the command line?
Have you tried using the vglrun command in linux? This uses the VirtualGL https://wiki.archlinux.org/title/VirtualGL tool to enable to use a graphic card for rendering in GeoDict.
For this to work you first need to install the VirtualGL to your linux system.
Let me know if this can resolve the issue.
nice to have you here as a new user.I assume you start GeoDict from the command line?
Have you tried using the vglrun command in linux? This uses the VirtualGL https://wiki.archlinux.org/title/VirtualGL tool to enable to use a graphic card for rendering in GeoDict.
Code Select
pathToGeoDict: vglrun geodict2023.shFor this to work you first need to install the VirtualGL to your linux system.
Let me know if this can resolve the issue.
#93
Basic functionality and features / Error message when trying to r...
Last post by djauffres - June 14, 2023, 03:33:46 PMGoodmorning,
I have issues to run geodict remotely (using ssh -X connection to a linux server). The server is under CentOS Linux 8 and here is the error message I am getting:
"Unexpected critical error: GLWidget::makeCurrent(): Current context does not exist or is not valid!"
Geodict runs perfectly when I am executing it locally on the server.
Any guess from where the issue could come from ?
Thank you
I have issues to run geodict remotely (using ssh -X connection to a linux server). The server is under CentOS Linux 8 and here is the error message I am getting:
"Unexpected critical error: GLWidget::makeCurrent(): Current context does not exist or is not valid!"
Geodict runs perfectly when I am executing it locally on the server.
Any guess from where the issue could come from ?
Thank you
#94
Basic functionality and features / Re: Visualization Questions
Last post by Roman Buchheit - June 05, 2023, 11:48:38 AMHello Aaron,
it's possible to set these visualizations. Let me answer your question assuming that you simulated the flow through the pores of a porous structure (see image 1).
[attachimg=1]
1.) To show a volume field in 2D view, load the "velocity" volume field. Then click on 2D view and in the camera tab, select Grid: "Structure Outlines" in the combobox. Now you see an outline of the structure, as shown in image 2.
It's now possible to modify the view: For example, you can deselect the structure by unchecking "Structure" in the corresponding tab in the visualization settings.
To enhance the outlines, you can set the volume field to transparent. Check the "Transparent" checkbox (image 3), with the "Edit ..." color map you can select the transparency that you prefer. The outlines are one pixel by default and appear quite slim. As one solution, you can either zoom out to show the whole structure smaller on the screen so that the lines will appear thicker in comparison to the structure size.
For a more controlled way, go to File --> Save Image as --> Select "Legend Placement: Attached", uncheck "Automatic Resolution" and set Zoom Factor e.g. to "2". Then, one voxel will be shown by 2x2 pixels and therefore the outline is half as thick as one voxel (image 4).
You can further play with Camera --> Depth Settings or add more points in the transparency of the volume field (e.g. setting the transparency of the volume field to 0 for velocities close to 0) as shown in images 5-6.
[attachimg=2]
2.) Streamlines in 3D view do not project on 2D view. Instead, to show the volume field lines in 2D view (e.g. the flow field lines) select "Schlieren" (image
and then the x position, where you want to show the projection of the flow.
Now you can increase the resolution (e.g. to 4) and select "Colorize".
Another way to show the structure is by selecting the clipping in X direction accordingly (see image 9).
Afterwards, you could fine-tune the 2D angle in the "Camera" tab and deselect the bounding box in the Visualization side bar -> Legends / Overlays -> Uncheck Bounding Box. (Image 10)
[attachimg=3]
[attachimg=4]
it's possible to set these visualizations. Let me answer your question assuming that you simulated the flow through the pores of a porous structure (see image 1).
[attachimg=1]
1.) To show a volume field in 2D view, load the "velocity" volume field. Then click on 2D view and in the camera tab, select Grid: "Structure Outlines" in the combobox. Now you see an outline of the structure, as shown in image 2.
It's now possible to modify the view: For example, you can deselect the structure by unchecking "Structure" in the corresponding tab in the visualization settings.
To enhance the outlines, you can set the volume field to transparent. Check the "Transparent" checkbox (image 3), with the "Edit ..." color map you can select the transparency that you prefer. The outlines are one pixel by default and appear quite slim. As one solution, you can either zoom out to show the whole structure smaller on the screen so that the lines will appear thicker in comparison to the structure size.
For a more controlled way, go to File --> Save Image as --> Select "Legend Placement: Attached", uncheck "Automatic Resolution" and set Zoom Factor e.g. to "2". Then, one voxel will be shown by 2x2 pixels and therefore the outline is half as thick as one voxel (image 4).
You can further play with Camera --> Depth Settings or add more points in the transparency of the volume field (e.g. setting the transparency of the volume field to 0 for velocities close to 0) as shown in images 5-6.
[attachimg=2]
2.) Streamlines in 3D view do not project on 2D view. Instead, to show the volume field lines in 2D view (e.g. the flow field lines) select "Schlieren" (image
and then the x position, where you want to show the projection of the flow. Now you can increase the resolution (e.g. to 4) and select "Colorize".
Another way to show the structure is by selecting the clipping in X direction accordingly (see image 9).
Afterwards, you could fine-tune the 2D angle in the "Camera" tab and deselect the bounding box in the Visualization side bar -> Legends / Overlays -> Uncheck Bounding Box. (Image 10)
[attachimg=3]
[attachimg=4]
#95
Digital Battery Development / Re: [GeoDict 2023] How can I s...
Last post by Roman Buchheit - May 19, 2023, 01:22:36 PMLet me pleaseanswer to this issue to show you how you can easily reflect the effect of different charging rates on the cell capacity in BatteryDict in GeoDict 2023.
The reached capacity during cell cycling is often defined by upper/lower cell voltages in real experiments. These upper/lower cell voltages are reached during the discharge/charge of a cell. The limitation of cell voltages prevents damage of a cell, e.g. by lithium plating at very low cell voltages or electrolyte decomposition at very high cell voltages.
In GeoDict 2023, the cut-off voltages can be provided as a boundary condition to stop a constant current charging simulation.
As an example, let us consider the delithiation of a NMC622 cathode vs a lithium reservoir using the "Charge Half Cell" functionality of BatteryDict. The cell potential of the half cell will increase during delithiation of the NMC622, i.e. we want to provide an upper cut-off voltage to stop the simulation. This can be done in the "Experiment" tab in the Edit parameters window of charge half cell. Please toggle the checkbox at "Use Upper Cut-Off Voltage" and enter the desired cut-off voltage. With the settings provided below the simulation will stop either when the upper cut-off voltage of 4.3 V is reached or when the final Electrode SOC of 5% is reached.
[attachimg=1]
You will see the effect when performing charging simulations with different C-rates: if you use higher C-rates/currents, the cut-off voltage might be reached at less transferred capacities. In the example, the cut-off potential of 4.3V was reached after a transferred charge of 0.423 µAh with the lowest current (2C), while larger currents reached the cut-off potential already after a transferred charge of 0.417 µAh (3C) and 0.402 µAh (4C).
[attachimg=2]
For further details regarding the cut-off voltage settings, please refer to the current BatteryDict User Guide.
The reached capacity during cell cycling is often defined by upper/lower cell voltages in real experiments. These upper/lower cell voltages are reached during the discharge/charge of a cell. The limitation of cell voltages prevents damage of a cell, e.g. by lithium plating at very low cell voltages or electrolyte decomposition at very high cell voltages.
In GeoDict 2023, the cut-off voltages can be provided as a boundary condition to stop a constant current charging simulation.
As an example, let us consider the delithiation of a NMC622 cathode vs a lithium reservoir using the "Charge Half Cell" functionality of BatteryDict. The cell potential of the half cell will increase during delithiation of the NMC622, i.e. we want to provide an upper cut-off voltage to stop the simulation. This can be done in the "Experiment" tab in the Edit parameters window of charge half cell. Please toggle the checkbox at "Use Upper Cut-Off Voltage" and enter the desired cut-off voltage. With the settings provided below the simulation will stop either when the upper cut-off voltage of 4.3 V is reached or when the final Electrode SOC of 5% is reached.
[attachimg=1]
You will see the effect when performing charging simulations with different C-rates: if you use higher C-rates/currents, the cut-off voltage might be reached at less transferred capacities. In the example, the cut-off potential of 4.3V was reached after a transferred charge of 0.423 µAh with the lowest current (2C), while larger currents reached the cut-off potential already after a transferred charge of 0.417 µAh (3C) and 0.402 µAh (4C).
[attachimg=2]
For further details regarding the cut-off voltage settings, please refer to the current BatteryDict User Guide.
#96
Digital Battery Development / [GeoDict 2023] How can I simul...
Last post by GeoDict Electrochmistry User - May 19, 2023, 01:12:55 PMIn an experiment, I observe capacities that depend on the charge rate, i.e. larger charge rates result in reduced capacity. How can I represent this observation in a BatteryDict simulation?
#97
Basic functionality and features / Visualization Questions
Last post by Aaron Widera - May 11, 2023, 04:41:07 PMDuring my usage I came across two questions on visualization settings in GeoDict:
- How can I show a volume field and a structure outlines in 2D view
- How can I show volume field lines (e. g. flow field stream lines) in 2D view
#98
Structural Material Modeling and Analysis / Re: Building complex non-crimp...
Last post by Droste - May 08, 2023, 05:20:43 PMHello Aaron,
that's exactly the information I was looking for. Thank you!
Best regards,
David
that's exactly the information I was looking for. Thank you!
Best regards,
David
#99
Structural Material Modeling and Analysis / Re: Building complex non-crimp...
Last post by Aaron Widera - May 05, 2023, 03:12:49 PMHello David,
I am glad to see someone new here.An overview of the possible Gad Objects and their handling can be found in our User Guide for GADGeo: https://www.geodict.com/fileadmin/UserGuide/GeoDict2023/GadGeo2023.pdf#nameddest=GadAdd
Can you have a short look and let me know if this is helpful or if you need further information?
Best Regards,
Aaron
I am glad to see someone new here.An overview of the possible Gad Objects and their handling can be found in our User Guide for GADGeo: https://www.geodict.com/fileadmin/UserGuide/GeoDict2023/GadGeo2023.pdf#nameddest=GadAdd
Can you have a short look and let me know if this is helpful or if you need further information?
Best Regards,
Aaron
#100
Structural Material Modeling and Analysis / Building complex non-crimp fab...
Last post by Droste - May 05, 2023, 02:57:52 PMHello,
When adapting a python script for the creation of non-crimp fabric structures, I encountered the problem that the notation of the object types cannot be derived directly from GeoDict.
So far, elliptical rovings were used (GeneralCruvedEllipticalFiber), where 4 diameters have to be specified. With rectangular (GeneralCurvedRectangularFiber), on the other hand, 4 side lengths are specified.
Is there an overview for the different types and which parameters have to be specified?
Best regards,
David Droste
When adapting a python script for the creation of non-crimp fabric structures, I encountered the problem that the notation of the object types cannot be derived directly from GeoDict.
So far, elliptical rovings were used (GeneralCruvedEllipticalFiber), where 4 diameters have to be specified. With rectangular (GeneralCurvedRectangularFiber), on the other hand, 4 side lengths are specified.
Is there an overview for the different types and which parameters have to be specified?
Best regards,
David Droste