Timofey Mukha
Timofey Mukha
It would be good to add these 2 things to source terms: 1. Possibility to write the source term as a field, for inspection. Useful in various debugging contexts. 2....
This is a suggestion to enhance all our json-based factories with a KNOWN_TYPES list with the names of all the types the factory can create. We can then output this...
We currently do pointer allocation before fields are in use, should switch to allocation in the request routine.
The compression example needs an update prior to the new release. It's a TGV but still uses the old case-file. @adperezm , could you take a look please?
Once we merge #962 we can add various source terms for users to enjoy. Which ones are good to have, let's list them here. It could be a relatively easy...
This PR currently has a working preview of a scalar simulation component. Feel free to play around :-). Some points * The case now doesn't own the scalar, and it...
This is a proof of concept of how user simcomps can be incorporated into the `neko_simcomps` object so that they are executed just like the ordinary ones. As a reminder,...
So, looping up to NEKO_MSH_MAX_ZLBLS goes through garbage. We should use assumed shape arrays and through if json reallocates to an array, which is too marge. Also, look into retiring...
Hi! I have for some time trying to find a way to have factories that can be extended with new derived types without modifying the code of the factory. The...
We have a very simple type for material properties now, that basically stores the rho, mu, cp and lambda. Once we have more than one scalar, this does not really...