Julianus Pfeuffer
Julianus Pfeuffer
Or both? Looks like your solution does kind of both. What would users get from that and what implications has the namespace package?
Yes that is also my opinion. Also, they are just a few kilobytes of python source code. Nothing compared to the rest of openms. UV will take care of installing...
Regarding docs. Ideally you parse the python doc strings of the Tool or something as we do with TOPPTool to create a page together with the CLI arguments written as...
Regarding docs. Ideally you parse the python doc strings of the Tool or something as we do with TOPPTool to create a page together with the CLI arguments written as...
The thing is, if it goes into OpenMS, it needs to be doxygen, not readthedocs :( But you can generate a markdown based doxygen file for every tool relatively easily....
@copilot lol ignoring the problem doesn't make it go away. Does Database suitability exe at least depend on Comet adapter in cmake?
@copilot hahaha you are full of trash again: https://github.com/OpenMS/OpenMS/blob/86457c9de1b913feef1ced055dbbcd3812e2d862/src/openms/source/QC/DBSuitability.cpp#L303
Makes sense. For the Deb package openms should be built with the USE_EXTERNAL_SQLITECPP flag, which it is not.
I think he means to write that info into the library, per transition so it can be changed depending on the noise level in that area (if known from external)
You have to decide if you want the param with underscores or camelCase. But it needs to be consistent!