[Ros]

Originally Posted by chriss85

I have tried to use the compiled version on Kubuntu 14.04, I'm getting the following error:
./DICE: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version 'CXXABI_1.3.8' not found (required by ./DICE)

I assume you're linking against some other version of libstdc++, what do I need and how to set it up? Some googling points to adding the path of the correct version to LD_LIBRARY_PATH.

Hi chriss,

thanks for the feedback.
Just install the build-essentials and liblapack3 before running DICE by executing:

sudo apt-get install build-essential
sudo apt-get install liblapack3

If you also want to see how the help system and the IDE works, install
the latest qt (https://www.qt.io/download-open-source/#section-2) and change the prefix-path in the qt.conf-File from
Prefix=thirdparty/Qt/
to
Prefix=<your_install_path>/5.4/gcc_64

Let us know if it works.

[chriss85]

That doesn't work unfortunately, both packages were already installed.
I assume that 14.04 might have an older version than 14.10?

[alexeym]

Hi,

According to Distrowatch[1] in 14.04 gcc is 4.8.2 (CXXABI_1.3.7), in 14.10 gcc is 4.9.1 (CXXABI_1.3.8). And according to gcc [2]:

The reverse (backwards compatibility) is not true. It is not possible to take program binaries linked with the latest version of a library binary in a release series (with additional symbols added), substitute in the initial release of the library binary, and remain link compatible.

1. http://distrowatch.com/table.php?distribution=ubuntu
2. https://gcc.gnu.org/onlinedocs/libst...anual/abi.html

[chriss85]

So I should install the latest GCC using the PPA (http://askubuntu.com/questions/42819...-4-9-on-ubuntu) ?

[Ros]

I am afraid Alexey is right about the backwards compatibility. I just tried to compile it again on Kubuntu 14.04 VM and there are also problems with the new version of vtk (v6.2).

So I should install the latest GCC using the PPA (http://askubuntu.com/questions/42819...-4-9-on-ubuntu) ?

I have just tested your solution and it works. But you should be careful updating gcc if you are working on something. After the update some things could stop working.

[goethals]

Hi Chris, Ros and everybody.

I am running CAE linux 2013 in ubuntu 12.04. I ran into the CXXABI_1.3.8 issue, and running the sudo build-escentials and liblapack3 did not eliminate this message. But the following command did work for me:

sudo apt-get install libstdc++6

I now don't have the CXXABI_1.3.8 message, but rather "Could not initialize the python core!"
Any advise?[/QUOTE]

[simo2777]

Hi.
I successfully installed DICE v.0.0.2-alpha on Ubuntu 14.10 and 15.04 following the instruction (Source code on http://dicehub.net/download/).
The installation ended without error, but I didn't understand how to run the program.
Is there a particular command to execute or is there a launcher file?
Can you help me?
Thank you in advance.
Simone

[Ros]

Hi Simone,

if you successfully compiled dice you must have created an executable with the name "DICE" in your build-folder. Just start it from the console with

./DICE

[simo2777]

Thank you for the fast reply.
I've just tried the command .DICE as indicated, but I received this message:
<Could not initialize the python core!>
It's strange because python3 works.
If there are some other advice I will appreciate it, in case I will wait until the new release.
Thank you for you kind help.
Best regards.
Simone

[Ros]

It's very difficult to tell what the problem could be. Most common issue is wrong use of qmake or some errors with the python environment (especially LD_LIBRARY_PATH). We are currently working on an installer and it should solve those issues.

[mkraposhin]

Hello Simone, Ros

This week me and my colleaugues tested DICE in 2 environments and got the same issue.

Originally Posted by simo2777

I've just tried the command .DICE as indicated, but I received this message:
<Could not initialize the python core!>

We found that after

sudo make install

command files are copied to the following directory structure

opt
|__main
|    |__bin
|         DICE
|_apps
|_core_apps
|_db
|_dice
|_libview
|_test

and as we found from source code python modules are searched relative to the folder that contains DICE binary. So our solution was to move necessary folders or make symbolic links on the same level as DICE binary.

[francois]

Hi all,

Any news on the DICE front ?
Is this very promising project still developed ?

Thanks
François

[francois]

Nobody ?

[wyldckat]

Greetings François,

I hope Rostyslav doesn't mind me sharing this, but back in February I invited them to give a training course at OFW11 about DICE and in his answer what this:

We are not yet sure how we will proceed with the project and with the current state of the development we can not really offer a training course. We are still developing a lot of new features and they are sadly not yet presentable.

I'm guessing that they took the project off from public eyes for a few months, given that spending time to give support on early on-going developments is counter-productive.

My suggestion is that if you can help them in anyway, contact them directly! They are likely very busy and possibly don't have enough time to come by the forum.

Best regards,
Bruno

[francois]

Thank you very much Bruno for your kind and informative answer.

Indeed it's maybe best to contact them directly to see if we can help them in anyway.

And if they have the time to read us maybe they can tell us how the community can help them ...

I wish them best luck for their awesome project !

Thanks again Bruno

Regards
François

[Ros]

Hello everyone,

many of you here have sent me a few emails and were asking about the state of the project. So after a long time since I posted here I wanted to give you a quick update.
First of all thanks for following the project and all your encouraging messages!

What happened?
A small history lesson about DICE:

• In 2013/2014 me and my colleague came up with the idea to develop DICE, a framework for simplified creation of user interfaces and utilities in the area of numerical simulations. The goal was to develop a tool which an engineer or a scientist can use to quickly create or automate processes and tasks, including a very easy to use and flexible GUI.
  
• In 2015 the first prototype was created in C++/QML and publicly released. The feedback was overwhelmingly positive and we decided to incorporate a lot of the proposals into a new version.
  
• In 2016 we started working on DICE full time, switched to Python for the DICE backend, simplified the user interface even more, changed the complete software architecture and developed our web platform.
  
• Now: The result of a few years of work is: DICE v18.01.2

What is DICE and what it isn't?
DICE is a framework (or even a prototype for a framework) for workflow automation/optimization and this means it is not a fully developed GUI for numerical simulations. It has more in common with frameworks such as AngularJS or React than with software like Helyx, Fluent or COMSOL. So please do not expect it to have all the OpenFOAM solvers, all the DAKOTA optimization strategies or all the functions you can find in Ansys products. But you can use DICE to quickly develop a very customized simulation tool. This also means you probably need to do it yourself or ask someone to do it for you.

What's new in this version?

• DPM (DICE package manager): With dpm you can now automate the build and install procedures for DICE packages.
  
• Distributed applications: In most cases numerical applications become extremely complex and have a lot of dependencies. In the new version you can now use virtual python environments to make sure that all package dependencies are satisfied.
  
• Server/client architecture: In the new version the applications in DICE are separate from the main DICE process. This means for example that every interaction in your GUI is a remote procedure call.
  
  • All the visualization is actually a compressed data stream and as long you are not using a 4k monitor you won't see the difference to a native integration.
  • This was implemented to make collaboration possible and has already been successfully tested: https://www.youtube.com/watch?v=3ni3Boq1Ycc
  • This feature also makes it possible to use libraries such as VTK directly in your package and work on your applications without the compilation procedure.
  • This also makes cloud deployment much easier.
• Some advanced features: diceProperties, diceSlots and diceTasks simplify the development of OpenFOAM applications: https://docs.dicehub.com/v18/guide/a..._features.html
  
• DICE tools: Python API between DICE and its applications. These tools can also be written in other languages, for example JavaScript, and can be used to communicate between applications in the browser and DICE. https://github.com/dicehub/dice_tools
  
• Some working examples:
  • PythonOCC app
  • STL import app
  • snappyHexMesh app
  • simpleFoam app
  • A demo video for the simulation of an ahmed body

What is DICEhub?
DICEhub is a web platform we developed to be able to discuss and share workflows. You can create groups and projects, upload packages, images, cases and workflows. The goal was to create something like github but for engineers ans scientists. Right now it is being completely restructured, but you can already test all the functions and give your feedback.

If you are interested in testing just DM me or write an email to info@dicehub.com.

What now?
You can download DICE, test it and give us some feedback. We are currently deciding on how to move forward. There are already a lot of great GUI solutions for OpenFOAM out there: Helyx, simFlow, SimScale or Visual-CFD, so we are discussing if we should go into a different direction with the framework and move away from CFD. If you some ideas for a pilot project or some suggestions for further improvements leave it here. Any feedback would be greatly appreciated!

Thanks in advance.

Best regards,
Rostyslav

[Shayor]

Hello Ros,so I have looked into your website and I think DICE is something very interesting.I wanted to know if could do coupling in it,I wanted to do an FSI simulation on blood flow,so please let me know about this.I wanted to do a publication using this amazing software.Thank you.