Using community plugins
The Pioreactor comes with a large set of functionality and behaviour to accomplish most projects. For example, continuous culturing, optical density reading, and stable temperatures are available out-of-the-box. However, the specifics and range of how people use bioreactors goes far beyond what we could ever cover. That's why Pioreactor has added a platform so that community members can make their own extensions and share them with others. We call these plugins. (Below is how to install plugins - if you are looking to create your own plugins, see here.)
From your Pioreactor's interface, the "Plugins" button on the left navigation bar will display all your currently installed plugins, and available plugins that meet standard requirements. We also encourage you to explore our forums for more plugins created by the community.
Automations installed via plugins
After installation, dosing, LED, and temperature automations will be available in the list of automations available to you.
Activities installed via plugins
After installation, an activity's state and settings will show up on each Pioreactor's card. Below, we've installed the pioreactor-air-bubbler plugin:
Managing on/off and settings are done just like any other job, in the Manage dialog:
You can uninstall plugins from the same page, too. These will remove the action on the Pioreactor's card, but won't delete the section in your config.ini. Also, if a SQL table was installed with the plugin, the table will not be deleted.
Alternative: putting Python files in the the
An alternative way to install a plugin is to place a Python file in the
/home/pioreactor/.pioreactor/plugins directory on the Raspberry Pi. This is good for one-off scripts or plugins you are demoing or testing. See more about writing and distributing plugins.