lsmbo / spectra-comp Goto Github PK

When we compare between two peaklist from proline projects ,It's advised to show the sequence of the matched spectra.

USE JPA and Hibernate to rewrite requests, it include the import of proline jar

use Datasource instead of driverManager...

Update retention time separately fro the reference spectra and tested spectra

Implement filters on jvafa-fx tableView to apply searches...

set compared spectra as mirror in graphics and rescale of peaks intensities

Build projects view as Proline studio project view

Compare between validate spectra and not validated spectra in two result sumamry from Proline databases ...

add settings of comparaisson spectra on main view

Use futures and callbacks to improve performances(especially to load spectra)

Add confirm dialog before to start spectra comparaison

So far the same deltamoz is used for both precursors and fragments
I would be more precise to have two different tolerance :
one for the precursor : precusordeltamoz
another for the fragment : fragmentdeltamoz
Moreover, both tolerance could be expressed either in Da (moz) or in ppm (10-6 x moz)

Cos theta min is a parameter easier to set as its values go from 0 (no matching) to 1 (perfect matching).

Find a better way to handle the retention from of spectra loaded from Proline databases.