ExposuresProvider / cam-pipeline

Data loading pipeline for CAM database
https://exposuresprovider.github.io/cam-pipeline/
MIT License
2 stars 4 forks source link

Many MeSH identifiers are reported as being unmapped #147

Open gaurav opened 2 weeks ago

gaurav commented 2 weeks ago

From our logs:

2024.06.17 22:08:52 [WARN] org.renci.translator.ctd.Model.actorType:56:20 - No mapping for MESH: MESH:D014750
2024.06.17 22:08:52 [WARN] org.renci.translator.ctd.Model.actorType:56:20 - No mapping for MESH: MESH:D007631
2024.06.17 22:08:52 [WARN] org.renci.translator.ctd.Model.actorType:56:20 - No mapping for MESH: MESH:C445068
2024.06.17 22:08:52 [WARN] org.renci.translator.ctd.Model.actorType:56:20 - No mapping for MESH: MESH:C025643
2024.06.17 22:08:52 [WARN] org.renci.translator.ctd.Model.actorType:56:20 - No mapping for MESH: MESH:C073734
2024.06.17 22:08:52 [WARN] org.renci.translator.ctd.Model.actorType:56:20 - No mapping for MESH: MESH:C016599
2024.06.17 22:08:52 [WARN] org.renci.translator.ctd.Model.actorType:56:20 - No mapping for MESH: MESH:C007262
2024.06.17 22:08:52 [WARN] org.renci.translator.ctd.Model.actorType:56:20 - No mapping for MESH: MESH:D008767
2024.06.17 22:08:52 [WARN] org.renci.translator.ctd.Model.actorType:56:20 - No mapping for MESH: MESH:C017803

I'm guessing this is because they are missing from chebi_mesh.tsv, but we can normalize these with NodeNorm (example for MESH:C007262). Will these get picked up later, or should we incorporate NodeNorm normalization into this conversion step?