Developer’s call, 31.05.2021

j.schmoelder · June 1, 2021, 8:37am

CADET Web

(@w.heymann)

Fixed styling of newsletter page
Added newsletter subscription note to main page
Cleaned up menus

Also, we got a short overview of ibt761 which hosts

cadet-web.de
forum.cadet-web.de
(eventually) conf-tool

Fix compile warnings by jayghoshter · Pull Request #76 · modsim/CADET · GitHub

Discussion on using C++17 standards for Cadet, spawned by the [[fallthrough]] fix for compile warnings in StringUtil.hpp:siphash().
Discussion on using REES: Essentially just have a file (apt.txt/requirements.txt/etc) that specifies the version of build tools and dependencies used.

Write out state for every unit operation separately. by schmoelder · Pull Request #73 · modsim/CADET

(@j.schmoelder, @j.hassan)

Cleaned up files which were accidentally committed (using git reset --hard vs git reset --soft)
Fixed input of INIT_STATE_Y for unit operations. Was using old and inconsistent interface which was extracting INIT_STATE_YDOT if length of INIT_STATE_Y was 2*NDOF but was still requiring the INIT_STATE_YDOT parameter to be present. Now, INIT_STATE_YDOT is correctly extracted from the parameter provider.
Added Exception if length of INIT_STATE_Y was not correct.
Started implementing getModelSlice() in IModelSystem.

github.com

modsim/CADET/blob/af4bced2dd4705e87bb5fdf75a278f4f08b9e985/src/libcadet/model/ModelSystemImpl.cpp#L283

    
      
          }
          
          
unsigned int ModelSystem::numPureDofs() const CADET_NOEXCEPT
          {
          	unsigned int dofs = 0;
          	for (IUnitOperation* m : _models)
          		dofs += m->numPureDofs();
          	return dofs;
          }
          
          
std::vector<int> ModelSystem::getModelSlice() const CADET_NOEXCEPT
          {
          	std::vector<int> index_stride;
          	unsigned int stride = 0;
          	unsigned int index= 0;
          	std::vector<unsigned int> dofs = 0;
          	unsigned int counter = 0;
          	for (IUnitOperation* m : _models)
          	{
          		dofs[counter]= m->numPureDofs();
          		stride = dofs[counter];

Open question: Can we generally format Error Messages with more information s.t. for example instead of

"Length of INIT_STATE_YDOT should be equal to NDOF"

we get (assuming NDOF is 24)

"Length of INIT_STATE_YDOT should be equal to 24"

Also we should revisit a lot of the places where the input is checked and add or improve error checking. See also Implement linting tool · Issue #28 · modsim/CADET.

w.heymann · June 1, 2021, 9:04am

How about

Length of INIT_STATE_YDOT MUST be equal to NDOF (expected 24)

Should implies optional which I don’t think is the case. This also tells you that it must be equal to the degrees of freedom and what that should be.

j.schmoelder · June 1, 2021, 9:05am

yes, agreed, that’s what I was aiming for. It’s just that I lack the knowledge how to format these Error messages in C++.

In Python, it would be something like

raise Exception('Length of INIT_STATE_YDOT MUST be equal to NDOF (expected {})'.format(NDOF))

w.heymann · June 1, 2021, 9:13am

f’Length of INIT_STATE_YDOT MUST be equal to NDOF (expected {NDOF})’ for Python

j.schmoelder · June 1, 2021, 9:16am

Yes, this also works, but as far as I know, the new style of formatting strings (using the .format() method) is preffered (see Python String Formatting Best Practices – Real Python)

Edit: I take that back. They both work. Just the ‘old style’ using % signs is no longer recommended.