I don't think we "fix" the release, i.e. we use the latest Ensembl release, but this might not always work.
On latest re-install, I noticed that e.g. that release.json uses 112, but that under DATA_PATH/annotation, annotation are versioned according to 110 (this is fixed on startup using the annotation import table). How can we check ensure consistency? I think the only place we really validate the expected assembly and the downloaded files is by checking default_coord_system_version in AssemblyService.
I don't know if we can fetch any release easily on Ensembl.
A clear and concise description of todo items.
Fix the assembly and annotation release so that they are consistent with the database release
eboileau
commented
4 months ago
Aims/objectives.
To check how exactly releases are handled.
I don't think we "fix" the release, i.e. we use the latest Ensembl release, but this might not always work. On latest re-install, I noticed that e.g. that
release.jsonuses 112, but that underDATA_PATH/annotation, annotation are versioned according to 110 (this is fixed on startup using the annotation import table). How can we check ensure consistency? I think the only place we really validate the expected assembly and the downloaded files is by checkingdefault_coord_system_versioninAssemblyService.I don't know if we can fetch any release easily on Ensembl.
A clear and concise description of todo items.