[Simbelmynë]

Hi,


This has been discussed previously, but I think it is interesting to once again lift this topic. How do you structure your CFD projects? It may be vastly different between different software. I try to keep a similar structure regardless of software, but this is not always possible. We also face problems of a heterogeneous hardware distribution across all users. Data is never stored centrally and in many cases not even case files since we do not have a standardized way of storing cases.


With the constant stream of feature-breaking updates it is also somewhat important to keep track of the version (looking at you OpenFOAM ).


Also in a more general sense, do you like to structure projects into a "per project" basis or do you group it into certain areas, e.g. multiphase flow / single phase flow (similar to how OF structured standard solvers) or perhaps car / airplane / chemical reactor etc. Or perhaps a combination of everything?


Do you use directory names with enough content to make someone accessing the information 10 years later understand what the project is about or do you use generic names that are connected to some kind of descriptive file? Is reuse of old cases common or very uncommon where you work? In my workplace almost all cases are developed from scratch, however this has some merit since part of the process is an education that is not trying to be efficient.



Btw, CFD is awsome!