Match MS problem
Posted: December 18th, 2018, 5:52 am
Hi,
When I make a template from an analysis, I used "create qualifier CLIC constraints When adding blobs to template". I flagged the "Match MS" checkbox and set the limits to min 600 and max 999. Then included identified target peaks from the blob table to the template table and saved the template. So far, so good, the target components are in the template. When I then match an other analysis against the template, a lot of targets are not found, although they are there for sure. When I select 'template mode' and right click on the blobs, I see that the Qualifier CLIC MS-Match is not between 600-999, but set to > 903 for instance (varying per blob). This has the consequence that a lot of targets are missed (nearest blob's CLIC constraint test failed). When I manually correct this value to > 600, then the targets are found. But then I have to correct all my target components in the template manually. Where is the initial CLIC MS-match (903-value from the example) coming from? It's not the library-fit score. Is there a smarter way to do this? I would like to set a general MS-matching against the template of say > 600 for all targets in one go.
When I make a template from an analysis, I used "create qualifier CLIC constraints When adding blobs to template". I flagged the "Match MS" checkbox and set the limits to min 600 and max 999. Then included identified target peaks from the blob table to the template table and saved the template. So far, so good, the target components are in the template. When I then match an other analysis against the template, a lot of targets are not found, although they are there for sure. When I select 'template mode' and right click on the blobs, I see that the Qualifier CLIC MS-Match is not between 600-999, but set to > 903 for instance (varying per blob). This has the consequence that a lot of targets are missed (nearest blob's CLIC constraint test failed). When I manually correct this value to > 600, then the targets are found. But then I have to correct all my target components in the template manually. Where is the initial CLIC MS-match (903-value from the example) coming from? It's not the library-fit score. Is there a smarter way to do this? I would like to set a general MS-matching against the template of say > 600 for all targets in one go.