Set initial parameters

[arindamsaha1507]

Main changes

I have added settings.yml that in principle should contain all the hard-coded values used in the simulation.

Further questions / decisions to be made

• Naming Convention: Currently kept as in the Matlab code. But it seems to be inconsistent.Do we bother changing it?
• Flags: After going through the programming logic, we must aim to reduce the number of flags being used.

[tkoskela]

Thanks, the structure (mostly) makes sense to me! I added a few comments on things we may not need.

I'm starting to learn towards more descriptive variable names (than PX2Tilde etc.) but that can be done later. I'm curious what was inconsistent about the naming convention? Do you mean the Uppercase vs lowercase names?

I think we should aim to drop the testing flags from this file as well and implement the tests properly. I feel like there are many more flags in the code that we will want to either move here or get rid of. I'm happy to add them later, unless you can find very obvious ones.

[tkoskela]

Should outputs also be here?

[arindamsaha1507]

Good point. I will add them. I will also keep the .mat formats for now... Just in case...

[arindamsaha1507]

Yes... sometimes the names start with uppercase (e.g. BaseData) and sometimes with lowercase (eg. hiHours0)...

[tkoskela]

Yes... sometimes the names start with uppercase (e.g. BaseData) and sometimes with lowercase (eg. hiHours0)...

Since we are starting from scratch, let's fix that. I would say we follow https://docs.julialang.org/en/v1/manual/variables/#Stylistic-Conventions, ie. variable names are lowercase with underscores when necessary for word separation.