Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fuse all parameter types? #140

Open
AtiyahElsheikh opened this issue Oct 25, 2022 · 1 comment
Open

Fuse all parameter types? #140

AtiyahElsheikh opened this issue Oct 25, 2022 · 1 comment
Labels
architecture changes concerning code organisation question Further information is requested

Comments

@AtiyahElsheikh
Copy link
Collaborator

Can work parameters (within the type WorkPars) be viewed as Demography parameters?

The question whether an internal architecture distinguishing demography from other elements (e.g. economy) is needed. If no, then Demography module does not look to be needed / distinguished. However, my intuition is that, indeed, economic parameters need to be placed within their own sub-modules. This would be useful in many situations, for instance, executing purely demographic simulations (without economic elements).

@AtiyahElsheikh AtiyahElsheikh added question Further information is requested architecture changes concerning code organisation labels Oct 25, 2022
@mhinsch
Copy link
Member

mhinsch commented Jul 7, 2023

It might be easier to simply fuse all parameter types a model uses into one (using e.g. CompositeStruct).

@mhinsch mhinsch changed the title WorkPars as demographic parameters ? Fuse all parameter types? Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
architecture changes concerning code organisation question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants