For niche codes like FPRE004, general search engines fail. Niche communities succeed.
| Question | Answer |
|----------|--------|
| Is the free edition truly “free” for commercial use? | No. The Community License restricts commercial redistribution. For any revenue‑generating product you must purchase a commercial license. |
| Can I use the free edition on a cloud VM? | Yes, as long as the VM is used for non‑commercial or research purposes. |
| Why is the data‑file size limited to 2 GB? | The limit protects the community tier from excessive resource consumption. The paid tier removes this ceiling. |
| Does the free edition receive security updates? | Critical security patches are back‑ported to the community branch. Minor feature updates are released quarterly. |
| Can I contribute a plug‑in to the official repository? | Absolutely. Fork the GitHub repo, add your plug‑in under plugins/, and submit a pull request. All contributions must be compatible with the MIT‑compatible license. |
| Is there a GUI? | The free edition ships only with a command‑line interface and Jupyter‑Notebook examples. A full GUI is part of the paid “FPRE‑004 Studio” bundle. | fpre004 free
| Aspect | Details | |--------|---------| | License Type | MIT‑compatible (source‑available, permissive). The free edition is released under the FPRE‑004 Community License, which permits personal, academic, and non‑commercial use without royalties. | | Redistribution | You may redistribute the compiled binaries with your own project, provided you keep the original license notice and do not claim the free edition as a commercial product. | | Commercial Use | Not permitted in the free edition. To use FPRE‑004 in a commercial product, you must purchase a commercial license that unlocks additional features and removes usage restrictions. | | Contribution | The community edition is open to pull‑requests on GitHub. Contributions must be compatible with the community license. | For niche codes like FPRE004, general search engines fail
The community edition supports dynamic plug‑ins written in C++ or Python. A plug‑in must expose a register() function that returns a dictionary of the operations it adds. | Aspect | Details | |--------|---------| | License
Skeleton C++ Plug‑In (example)
#include <fpre004/api.hpp>
extern "C" void register_plugin(fpre::Registry& reg)
reg.add_operation("my_custom_filter", [](const fpre::Tensor& input)
// Simple threshold filter
return fpre::where(input > 0.5, input, 0.0);
);
Compile with:
g++ -shared -fPIC myfilter.cpp -o myfilter.so -I/path/to/fpre/include
Drop myfilter.so into $HOME/.fpre004/plugins and restart the engine; the new operation appears under fpre.custom.my_custom_filter.