Skip to content

Releases: ohnosequences/db.rnacentral

db.rnacentral v0.13.1

14 Nov 12:20
7792f36
Compare
Choose a tag to compare

0.13.1

This bugfix release renews the support for the version 9 of RNACentral, adding integrity checks to it. This let us simplify the transfers, as we can assume from now on that the files from all supported versions contain metadata with hash information.

db.rnacentral v0.13.0

12 Nov 11:50
ba4dfb9
Compare
Choose a tag to compare

0.13.0

This version refactors the whole data release process:

  • aws-scala-tools was removed and s3 and files were added as new dependencies.
  • The release process is now local: no EC2 instances are run when releasing a new version of the package.
  • The release process was refactored out of tests and reimplemented in an object on the main code.
  • The definition of the data was slightly improved.
  • The old data versions were removed from the code and the current test versions are being uploaded to an unstable subdirectory in S3.
  • A new test was implemented to check that all supported versions are in S3 as expected.

From now on, the data release process should look something like the following:

  1. Add a new object that extends Version in src/main/scala/data.scala; e.g., case object _11_0 extends Version("11.0")
  2. Perform the mirror through the method release.mirrorNewVersion; e.g., through an sbt console:
scala> import ohnosequences.db.rnacentral._
scala> release.mirrorNewVersion(Version._10_0, new java.io.File("~/localDir"))
  1. Prepare a new release of the repository by writing release notes in the corresponding file in notes; e.g. in notes/0.14.0.markdown
  2. Make the release of the repository, that checks that all declared versions of the data exist and are correct. This is done through the sbt release task; e.g., with sbt release minor

db.rnacentral v0.12.2

30 Aug 10:41
Compare
Choose a tag to compare

0.12.2

Up to RNACentral v7, the sequences and ID mappings files were aligned. From v8, the ID mappings file is no longer ordered.

This release fixes the issues caused by this change, modifying the code to take this into account and removing the tests that checked that the files were actually aligned.

However, this fix has increased both the time and the memory needed to run the ReleaseOnly tests, as the whole ID mappings is now stored in-memory as a map linking the RNA IDs with the annotations.

For more information, see pull request #46.

db.rnacentral v0.12.1

17 Jul 12:35
Compare
Choose a tag to compare

0.12.1

Updates to RNACentral v9.

db.rnacentral v0.12.0

17 Jul 12:11
Compare
Choose a tag to compare

0.12.0

Updates to RNACentral v9.

db.rnacentral v0.11.1

28 Nov 14:56
Compare
Choose a tag to compare

Hopefully fix bug with S3 addresses.

db.rnacentral v0.11.0

28 Nov 14:36
Compare
Choose a tag to compare

RNACentral 7.0

See ftp://ftp.ebi.ac.uk/pub/databases/RNAcentral/releases/7.0/release_notes.txt

db.rnacentral v0.10.1

13 Nov 20:24
Compare
Choose a tag to compare

Minor bugfixes related to the DB generation API:

  • Fixed s3 client shutdown
  • Fixed blastdb out name
  • Fixed FASTA files iterator
  • Made down/uploads failable with proper s3 client shutdown in the end

db.rnacentral v0.10.0

25 Oct 12:12
Compare
Choose a tag to compare
  • #30: Updated to RNAcentral v7

db.rnacentral v0.9.0

13 Jan 15:01
Compare
Choose a tag to compare
  • #26: Updated to the RNAcentral v6.0 release
  • #27: Temporary bugfix: added parse_seqids manually to BLAST db generation
  • #29: Some minor changes (see PR)