Skip to content
Snippets Groups Projects
  1. Sep 27, 2015
    • Vermaat's avatar
      Bi-directional cachinig of transcript-protein links · 8bbbc3a8
      Vermaat authored
      Previously transcript-protein links were assumed to always be
      indexed by transcript, and cached entries were allowed to have
      a `null` protein (meaning caching the knowledget that there is
      no link for this transcript).
      
      Now we can cache links in both directions. Both transcript and
      protein are allowed to be `null` (but not at the same time),
      and the protein column has a new unique constraint.
      8bbbc3a8
  2. Sep 11, 2015
  3. Sep 07, 2015
  4. Aug 11, 2015
  5. Aug 10, 2015
  6. Jul 16, 2015
  7. Jul 03, 2015
    • Vermaat's avatar
      Use chardet instead of cchardet · dedad241
      Vermaat authored
      Issue #50 showed a problem in our file encoding detection, caused
      by our cut-off for the confidence as reported by the cchardet [1]
      library:
      
          >>> import cchardet
          >>> s = u'NM_000052.4:c.2407\u20132A>G'
          >>> b = s.encode('WINDOWS-1252')
          >>> cchardet.detect(b)
          {'confidence': 0.5, 'encoding': u'WINDOWS-1252'}
      
      We require a confidence stictly greater than 0.5 and default to
      UTF8 otherwise.
      
      If, however, we try the same thing using the chardet [2] library,
      we get a higher confidence for the same string:
      
          >>> import chardet
          >>> chardet.detect(b)
          {'confidence': 0.73, 'encoding': 'windows-1252'}
      
      So the two obvious ways to solve this are:
      
      1. Lower the confidence threshold.
      2. Use chardet instead of cchardet.
      
      We implement the second solution here, since it also removes a C
      library dependency and we are not worried by performance.
      
      Of course the detected encoding remains a guess which can still
      be wrong!
      
      [1] https://github.com/PyYoshi/cChardet
      [2] https://github.com/chardet/chardet
      
      Fixes #50
      dedad241
  8. May 01, 2015
  9. Apr 30, 2015
  10. Jan 30, 2015
  11. Dec 16, 2014
  12. Dec 11, 2014
  13. Dec 10, 2014
    • Vermaat's avatar
      Compilation of developer documentation on Read The Docs · 667f8799
      Vermaat authored
      We use a separate `doc/requirements.txt` file for building the
      documentation. Since on Read The Docs where we cannot install
      packages depending on C libraries, we mock these packages in
      `doc/conf.py` and omit them from the requirements.
      667f8799
  14. Dec 08, 2014
  15. Nov 04, 2014
  16. Oct 20, 2014
  17. Sep 06, 2014
  18. Aug 27, 2014
  19. Aug 26, 2014
  20. Jul 04, 2014
  21. Jul 01, 2014
  22. May 13, 2014
  23. Apr 30, 2014
  24. Apr 25, 2014
  25. Apr 23, 2014
    • Vermaat's avatar
      Move to Sphinx for developer documentation · 2f33e62c
      Vermaat authored
      This is quite a large commit, touching many things related to developer
      documentation. It is all focussed on getting as much of this as possible
      into the new Sphinx-based documentation.
      
      Some highlights:
      
      - Start Sphinx-based developer documentation, including fairly complete
        instructions for installation and configuration.
      - Remove epydoc API docs.
      - Rework some docstrings to conform to reStructuredText, so they can be
        used in the API docs generated by Sphinx.
      - Move all of the top-level text files to reStructuredText so they can
        linked from the Sphinx-based docs and for consistency.
      - Remove many obsolete things from the extras/ directory, including old
        installation scripts and migrations.
      
      Many of the installation related documentation and scripts are removed
      or adapted in light of the new automated deployment using Ansible.
      2f33e62c
  26. Jan 30, 2014
  27. May 21, 2013
  28. Apr 08, 2013
  29. Jan 03, 2013
  30. Dec 06, 2012
Loading