-
Notifications
You must be signed in to change notification settings - Fork 16
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
PFEM-DEM GUI needs to be updated like Fluid-DEM GUI #645
Comments
Hi @jginternational , have you had some time to look into this? I add @joaquinirazabal as he is also interested in this issue. |
@ipouplana I'm trying to understand the example Small Box and the first I see is that the json is difficult to be generated. Look at I know that the coupling strategy is not the same but for me it's almost impossible to know there do the paremeters come from |
Hi @jginternational , I know that the ProjectParameters.json structure is not canonical, but it should follow the same concept as in the Fluid-DEM GUI (eulerian fluid-DEM) that Guillermo Casas, Ferran, you and me designed some months ago here FluidDEM |
Hi! How is this issue, is the interface working? It would be useful for us in Madrid. Thanks! |
Looks like someone should take the lead of this and set up a meeting with @jginternational to actually implement it. I think that copying from Fluid-DEM should not be hard. I suggest @MZecchetto , as you are used to do it manually, Max, and you know better than anyone what the GUI should do. |
Hi @jginternational ,
@AFranci , @maceligueta , @ipouplana and me have met and realized that the PFEM-DEM GUI is not updated according to the recent changes in the SwimmingDEMApplication.
The PFEM-DEM GUI should be almost identical to the current eulerian Fluid-DEM GUI, but replacing the eulerian fluid GUI by the PFEM fluid GUI. Could you work on that?
In the meantime, I can generate the input files of the euleran Fluid-DEM GUI and the PFEM-DEM GUI and combine them manually, but it is actually not very comfortable.
The text was updated successfully, but these errors were encountered: