From: Fredrik L. <Fre...@im...> - 2008-03-04 11:31:19
|
I've just followed this thread briefly since I have no intention to generate these index files, so I should probably just keep quiet. Anyway, how would it be to enforce a naming convention for spectrum ids so that the native scans can be extracted in the case when there is just one scan as the source for the spectrum? I think this is what Matt proposes, and it seems fine to me. That way there is no need to change the main schema or idx. The spectrum id could be regex checked and that's all. For example: S1F1C1 would mean scan1, function 1, cycle 1, while S1 just means scan 1. One could add a regex check to the main schema for the spectrum id, for example "S[0-9]+(F[0-9])?" for scan and optional function. I am not a regex expert, but I am sure someone could come up with a regex which is at least rather future safe for native scan references, and which allows some local variants to encode other information in the spectrum ID. This could also be used for the acquisition external spectrum id ref. Regards Fredrik |