lipidxplorer issueshttps://gitlab.isas.de/lifs-public/lipidxplorer/-/issues2020-03-02T14:13:25Zhttps://gitlab.isas.de/lifs-public/lipidxplorer/-/issues/29Check in mzML, whether isolation window is the precursor isolation window is ...2020-03-02T14:13:25ZNils HoffmannCheck in mzML, whether isolation window is the precursor isolation window is the same as in Thermo RAWhttps://gitlab.isas.de/lifs-public/lipidxplorer/-/issues/28Update LipidXplorer Wiki, describe entry paths and application use cases2020-03-02T13:32:03ZNils HoffmannUpdate LipidXplorer Wiki, describe entry paths and application use casesThe discussion showed, that we need to be able to guide users to choose, whether they should choose the web-application, the standalone LipidXplorer, or PeakStrainer as a preprocessing / size reduction tool. Also, we should explain the o...The discussion showed, that we need to be able to guide users to choose, whether they should choose the web-application, the standalone LipidXplorer, or PeakStrainer as a preprocessing / size reduction tool. Also, we should explain the options, e.g. Docker image, Standalone, etc.
Thus, the Wiki needs to contain a new page: choosing your path with LipidXplorer or something along those lines.https://gitlab.isas.de/lifs-public/lipidxplorer/-/issues/27Evaluate LipidCreator mfql integration2020-03-02T10:40:17ZNils HoffmannEvaluate LipidCreator mfql integrationLipidCreator could be used as an "editor" for selection of lipid parameters to finally create mfqls following a certain basic pattern.LipidCreator could be used as an "editor" for selection of lipid parameters to finally create mfqls following a certain basic pattern.https://gitlab.isas.de/lifs-public/lipidxplorer/-/issues/22Memory Handling / Clear Memory2020-12-04T09:45:34ZDominik SchwudkeMemory Handling / Clear Memorywith 1.2.8 we fill the RAM up fast. Unfortunately, every action by LX incrementally increase the blocked RAM. We should find a way that LX clears RAM after action.with 1.2.8 we fill the RAM up fast. Unfortunately, every action by LX incrementally increase the blocked RAM. We should find a way that LX clears RAM after action.LipidXplorer 1.2.9Eduardo MirandaEduardo Mirandahttps://gitlab.isas.de/lifs-public/lipidxplorer/-/issues/20Include postprocessing tab in LipidXplorer2019-10-11T16:03:00ZNils HoffmannInclude postprocessing tab in LipidXplorerClosely linking LipidXplorer workflow to lab-specific post-processing:
e.g.:
* Kai‘s FA model correction
* general cleanup / filter / quantification module (Postman, ...)
* CloverClosely linking LipidXplorer workflow to lab-specific post-processing:
e.g.:
* Kai‘s FA model correction
* general cleanup / filter / quantification module (Postman, ...)
* CloverLipidXplorer 1.2.9https://gitlab.isas.de/lifs-public/lipidxplorer/-/issues/19mzTab-M output support2019-10-11T16:04:33ZNils HoffmannmzTab-M output supportLipidXplorer 1.2.9