Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a simple model for spot location and MALDI target ID #2108

Merged
merged 1 commit into from
Feb 27, 2025

Conversation

Mailaender
Copy link
Contributor

There is more to model here as depicted in

@XmlElement(required = true)
private OntologyEntry plateManufacturer;
@XmlElement(required = true)
private OntologyEntry plateModel;
private Pattern pattern;
@XmlElement(required = true)
private List<Spot> spot;
@XmlAttribute(name = "plateID", required = true)
@XmlSchemaType(name = "positiveInteger")
private BigInteger plateID;
@XmlAttribute(name = "spotXCount", required = true)
@XmlSchemaType(name = "positiveInteger")
private BigInteger spotXCount;
@XmlAttribute(name = "spotYCount", required = true)
@XmlSchemaType(name = "positiveInteger")
private BigInteger spotYCount;

but spot/plate as text seems to be the common denominator between all the MALDI formats.

There is also overlap between microplates, which could be addressed in the future.

@eselmeister eselmeister merged commit a774df6 into eclipse-chemclipse:develop Feb 27, 2025
3 checks passed
@Mailaender Mailaender deleted the maldi-plate branch February 27, 2025 14:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants