Skip to content

Add MiBiPreT-wide documentation with details of best practices for using the constituent packages #1

@raar1

Description

@raar1

We had discussed before about having some documentation for the prediction tool (as a whole, i.e. not individual packages). This would describe how and why to use these packages together to perform analyses.

It would be nice also to have some "best practices" in the sense of basic guidelines about when it is best to use a given level of modelling (i.e. package). When should you use mibitrans (what are the physical regimes of validity and how do you know if that is true for your case)? When should you use mibiremo, mibiscreen etc?

This does not need to be a huge amount of information, but it could help potential users understand why we have split this Prediction Tool into several packages with different functionality.

Concrete examples (ideally using some real field data) of where a given modelling approach works and where it doesn't work would also be good.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions