> For the complete documentation index, see [llms.txt](https://pecan.gitbook.io/betydbdoc-dataentry/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pecan.gitbook.io/betydbdoc-dataentry/acknowledgements.md). # Acknowledgements ## Developers Patrick Mulroony originally implemented the data entry interface, and it is currently maintained by Scott Rohde, with Rob Kooper playing a key role in the development of functionality required to model ecosystems within PEcAn. Andrew Shirk and Carl Crott have contributed (see [visualization on GitHub](https://github.com/PecanProject/bety/graphs/contributors)). ## Contributors Many data entry technicians (undergrads) have contributed to the implementation and development of the interface and documentation. These includee Moein Azimi, David Bettinardi, Nick Brady, Emily Cheng, Anjali Patel, along with other members of the EBI Feedstock Productivity and Ecosystem Services modeling group. ## Funding Sources * Energy Biosciences Institute * Department of Energy ARPA-E TERRA * National Science Foundation --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://pecan.gitbook.io/betydbdoc-dataentry/acknowledgements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.