In the source code version of Segment you can incorporate your developed plugins. Please see the Technical Manual for Segment for more details.
The developer has full rights to their plugins and may or may not release them under license terms they find appropriate as long as it does not conflict with license by Medviso AB.
We encourage users to release their plugins freely available for research purposes along with the general intentions of Segment. Freely available plugins can be incorporated in the base distribution of Segment if requested by the author and the plugin meets quality requirements.
You are not able to by yourself compile your developed plugins as part of Segment. If you are interested in a commercial distribution of your plugin please contact sales@medviso.com to discuss a partnership.
You may not distribute Segment along or bundled with your plugins, unless granted by Medviso AB.
- Start by forking this repository. Forking means that you create your own copy of Segment on Github.
- Happy hacking!
- When/if you want to submit your work to us, push your changes to a topic branch in your forked repository and submit a pull request and we'll have a look at your code. If we think there is some more organization needed, we'll help.
- Found a bug? Please let us know by opening an issue in the tracker!
- Please have a look at the coding standards in Chapter 6 of the tech manual.
- The tech manual and the Open Access Segment paper should give you an overview on how things work internally.
- You can also look at some of the existing plugins, like plugin_calibrate, plugin_summarize and the basic template plugin_template to get started.
- Organize your code as a single file source/plugin_pluginname.m (to get an item in the plugin menu).
- If you want additional files, put them in a single package directory source/+pluginname.
- Use the Matlab package mechanism instead of addpath.