You should be able to show certain mesh formats in Paraview directly. DEME can output the OBJ mesh files you load into it as VTK files for Paraview to render, too.
There is no openGL or irrlicht integrated since for the simulation size that DEME is intended to handle, real-time visualization is quite impossible. We might add some GPU-based rendering utilities later. Right now, the rendering relies on your own choice of CSV post-processing tools. I personally just use Paraview. You can use the XYZ information to create 3D points then use the radius to scale the glyph filters created based on these points. You can potentially set up remote interactive access using Paraview if the simulation runs on clusters, and this is usually fast for a quick check of results. I also use Blender's Python wrapper to produce renderings for publications, as it's convenient to run on clusters and you can leverage GPUs. Ruochun On Thursday, September 26, 2024 at 11:25:41 AM UTC+8 [email protected] wrote: > Thank you for the continued insight. We got it working and exported the > CSV files for a quick little proof that it worked! Ill need to learn how to > use paraview better if we are gonna have solid bodys involved im sure. I'm > guessing open GL or irrlicht is not available for live rendering view for > the DEME engine yet? And once we figure out how to import our geometry into > the program (we are importing a conveyor) what would be your best > recommendation as to being able to tweak the file quickly without having to > wait an hour to see if it worked or not. or would that be the post > processing module (i.e. blender) that we could use to see that quicker? Let > me know your thoughts. > > Thank you for the help, we are making some serious progress! > > best > > Liam > > On Monday, September 23, 2024 at 10:47:53 AM UTC-5 Ruochun Zhang wrote: > > Hi Liam, > > I don't think I fully understand the problem here. > > If you want to know how to run the demos yourself, then most of them > require DEME alone, not Chrono. You just have to finish the "Compilation" > section. You need Chrono only when you want to do a co-simulation, where > the problem requires more than a DEM solver. For most DEME demos, you can > find their executables in DEM-Engine/build/bin, and they should be directly > runnable. If they are not there, the compilation is incorrect. One > improvement I can suggest is that you don't have to put DEM-Engine inside > the build directory of Chrono since it's a build directory; just put it > under liam-murray/ like Chrono. > > If you would like to try building a co-simulation between DEME and Chrono, > then you should follow the steps detailed in the "Install as library" > section (and yes, one of the steps is doing ENABLE_DEME_TESTS). In that > case, you are building some scripts in chrono-projects and linking against > an installation of Chrono and DEME, which are not the demos that come with > DEME or say the ones you saw in the Box folder. They are some numerical > tests that are quite big and I put them there to demonstrate > co-simulations. I am not sure what you meant by "not calling the demos you > previously built". They are not supposed to call anything. > > If you are in fact having trouble with the visualization then that's a > different discussion. > > Thank you, > Ruochun > On Monday, September 23, 2024 at 10:41:13 AM UTC+8 [email protected] > wrote: > > Good evening, > > I got a ubuntu native linux install of chrono working all of the regular > demos work as expected, thank you again for the direction on that. > > I have achieved a clean install of the DEME using the single sphere > collide as it outputs a lot of data as described in the git hub page. > And when initializing the ccmake gui i have also achieved the > ENABLE_DEME_TESTS ON but it doesnt seem to be calling the demos i had > previously built when i compile the new build through the ninja, (i have > all the directories for open GL, GLEW, irrlicht, etc working) > current file paths im doing when i do the ccmake command > "/home/liam-murray/chrono/build" > this is where DEME successfully built > "/home/liam-murray/chrono/build/DEM-Engine/build/bin" > i even tried modifying the cpp file of the rotating drum DEME demo to > include open GL or irrlict to see if something displayed live for frames > but it didnt work > > im at a little bit of a road block, i know we are close to seeing the > same demos you have on the box.com for the DEME demos, they all run, we > just need to see them. > > thank you for your time, i really appreciate it! > > best, > > liam > On Wednesday, September 18, 2024 at 11:39:36 AM UTC-5 Liam Murray wrote: > > Thank you I appreciate it! Ill reach out if I run into any other issues, > you are a big help! > > best, > > On Wednesday, September 18, 2024 at 11:21:59 AM UTC-5 Ruochun Zhang wrote: > > Hi Liam, > > I am not aware of a video tutorial, but others might want to correct me. > The simple is probably just following the web page tutorial > <https://api.projectchrono.org/tutorial_install_chrono.html>. It contains > instructions for both Windows and Linux. And I think it's smart to use > command lines more on Linux, in which case you can skip step 4 "Install a > GIT client", and for other steps just make sure to follow the instructions > for Linux. > > Thank you, > Ruochun > > On Wednesday, September 18, 2024 at 11:10:07 PM UTC+8 [email protected] > wrote: > > Good afternoon, > > I appreciate the quick response. And we all appreciate your dedication to > project chrono! > > I will have to look into a native linux install, I haven't had any > experience other than some WSL or VMs. As we are following the chrono > tutorials for getting that set back up, would it still be similar to the > windows install but obviously doing more sudo apt install or calling > directories. Is there video tutorials that walk through a native linux > install for this if you know? > > Thank you for your attention > > On Tuesday, September 17, 2024 at 12:18:31 AM UTC-5 Ruochun Zhang wrote: > > Hi Liam, > > Thank you for reaching out. Unfortunately, the problem is that DEME (but > not other Chrono modules) does not run on Windows. I suggest that for now, > use a native Linux machine to run DEME-related applications (don't use WSL > as the problem is on WSL too). When this issue is fixed I'll send you a > notification, but there is no clear timelines for that. > > Thank you and let me know your other questions, > Ruochun > > On Monday, September 16, 2024 at 10:50:11 AM UTC+8 [email protected] > wrote: > > Good afternoon all, hope this finds you well. > > recently got into project chrono, i have a clean install of the regular > repository and now im trying to get the DEME Engine going to do more > particle simulations. I'm able to open the simulator-multi-gpu.sln with > all of the demo files to go with it, all of them did get built with a .exe > file in the bin folder but im having trouble running the simulations, it > keeps coming up with this 0xc0000006 after compiling the environment i > think? I attached the txt file of when i built the repository from visual > studios developer cmd. I tried my best following the tutorial on chronos > website and github page and i cant seem to get the cmake GUI going with > enable_deme_tests or those other things to pop up when i compile > everything. Do i have the right directories selected? im not sure, i would > appreciate some input as im sure its just a simple mixup and a second pair > of eyes would help [image: Screenshot 2024-09-15 212536.png][image: > Screenshot 2024-09-15 212710.png] > > -- You received this message because you are subscribed to the Google Groups "ProjectChrono" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/projectchrono/862f8989-e9b2-4451-9944-4236666c2f6fn%40googlegroups.com.
