(TEMPLATE) Module name or title including a useful description of module. Max. 100 characters.

YEAR-Surname-000, (Last updated: 1983-04-18)


Authors

Surname, Name (with no accent marks, first upper-case letters, and surname matching the id and root directory name) (Author, Compiler, Contributor, Copyright Holder, Creator, Thesis Advisor, Translator)


Module files

Module type

Algorithm

Languages

NetLogo

Tags

Modelling: agent initialisation   grid initialisation   time initialisation
Programming: Functional   Point-free style
Regions: Global
Periods: Palaeolithic
Subjects: diffusion

Input and output

References

Epstein, Joshua M. 2008. “Why Model?” Journal of Artificial Societies and Social Simulation 11 (4): 12. http://jasss.soc.surrey.ac.uk/11/4/12.html.
Romanowska, Iza. 2021. Agent-Based Modeling for Archaeology. Electronic. SFI Press. https://doi.org/10.37911/9781947864382.

README

Module name or title

by FULLNAME (NASSA submission 🚀)

Description of what the module does. It should expand the information already given in the name/title.

License

Add any default short text about license here, if license recommends it or offers badges. For example, if using the MIT License, naming it directly will be enough as long as the LICENSE file is present:

MIT

References

Use a print out version of the references in references.bib (any bibliographic convention). Supress section if there are no references. For example, using APA 7th edition style:

Epstein, J. M. (2008). Why Model? Journal of Artificial Societies and Social Simulation, 11(4), 12.

Romanowska, I. (2021). Agent-Based Modeling for Archaeology (Electronic). SFI Press. https://doi.org/10.37911/9781947864382

Further information

Add as many design details, instructions, and demonstrations as possible, particularly information that is not included in NASSA.yml. If the information is included as markdown or html files in the documentation folder, add links to them here (if they are absolute URLs inside the module directory, remember to update them once the module is integrated to the library).

See full list of documentation resources in documentation.