Tags give the ability to mark specific points in history as being important
  • CanDiD-2.0.0   Stability is around the corner
    Release CanDiD-2.0.0

    General informations

    • CanDiD_IHM project has been merged into this project to facilitate deployment instructions.

    CanDiD_IHM changes

    • Possibility to have colored header columns (20 colors available : red, pink, purple, deep purple, indigo, blue, light blue, cyan, teal, green, light green, lime, yellow, amber, orange, deep orange, brown, grey, blue grey, no color)

    CanDiD changes

    • Added an assembly table on which variants are defined
    • Variants are now defined by their chromosome, pos, ref, alt in the db
    • New gene panel table to help users designing requests
    • Corrected a bug that could slow down the requests when you would insert different values of a same annotation for one variant
    • Possibility to configure the annotations to be displayed in 20 different colors as a header in the web interface
    • New command line tools to :
      • insert or extract gene panels from the db
      • insert or extract annotation configurations from the db
      • insert samples, variants and their annotations into the db from an annotated VFC file
      • several purge commands detailed in the wiki
  • CanDiD_1.5.4   works with CanDiD_IHM 1.5.4
    00e79d8f · Bug with vsv id ·
    Release CanDiD_1.5.4


    • History functionality fully repaired
  • CanDiD_1.5.3-beta   Hotfixes

    Corrected 'validation_serie_name' in the last missing spots

  • CanDiD_1.5.2-beta   works with CanDiD_IHM_1.5.0-beta


    • Corrected wrongly renamed variable in migration 0010


    • Deleted migrations FIXME that was causing some issues


    • Added a migration correcting missing joins in getData and getVariantForValidation requests
  • CanDiD_1.5.0-beta   works with CanDiD_IHM 1.5.0

    Release Notes:


    • Change background image on login page with more recent one
    • Change verbose names on many models and admin experience to be more user-friendly
    • Fixed some templates issue in the global settings


    • New AbstractModel "TimeStampedModel" to auto-generate insert_date and update_date fields on models and make their update automatic
    • New abstract model "AuditStampedModel" implementing django-simple-history package to track model instance history
    • Changed Model "PlatformT" to support information sharing between platforms and ValidationSerie creation modes
    • Changed db_index for "SampleT" model to speed up the request time on sample_class and quality_check
    • Changed "SampleT" set_capture_id to be a ForeignKey
    • New model "ValidationSerie" to merge the validation method between SerieT and SampleGroup
    • Changed "AnnuaireT" model fields "cle" and "valeur" fields so they can be blank or null
    • Added support for datamart with ValidationSerie (not fully tested)


    • Put all unused / commented models at the end of the file
    • Added new fields to model "UserProfilT" to reflect the new permissions with ValidationSerie and PrivateVariantAnnotation
    • New model "PrivateVariantAnnotation" to handle private annotation at variant level for each platform
    • Changed model "VariationTypeT" to be variant and platform specific plus some control on the order (display weight)
    • Changed variants field of "VariationTypeT" model to null=True so you can create and edit variation types that are not already associated with variants
    • Changed swab_confirmation_analysis choices in model "ValidationSampleVariantT" to be configurable in the settings via the SWAB_CONFIRMATION_ANALYSIS_CHOICES constant
    • Added field locked_interpretation to model "ValidationSampleVariantT". It can be used as patient given interpretation for a variant at a given time


    • Added a new method get_validation_data_from_db that will replace get_validation_data at a later date and that is using sample or ValidationSerie to request the database


    • New function to generate sample report, validation_sample_summary, it returns an xlsx for one sample or a zip with xlsx inside when the input is a list of patients. The report contains tabs depending on the input demand
    • New function to compute variant occurrences in the database and not dependent on the content of the database


    • "Annuaires" views are now sorted by object name.

    [base_api]: New application to merge all base api stuff

    • Currently holds all new viewsets, serializers and routers for Sample, Platform and ValidationSerie

    [candid_api]: New application to merge all candid API stuff

    • Currently holds all new viewsets, serializers and routers for VariantionClass, VariationTypeT and PrivateVariantAnnotation

    [candid_db_engine]: New Application to merge all DB functions

    • Migrations have been reworked so that all DB functions modification are now in this app. By doing this, we also have a better insight on what's in the migrations
  • prod_cfb_1.1.3   mise en production le 19/09/2016 - tag effectuer après execution des tests.
  • recette_v1.1.2   + Gestion des analyses bioinformatiques en cours
  • v_1_1_1_demo   récupération du code de la v1.1 quasiment finalisée pour installation de la démo.
  • v_1_1_demo   récupération du code de la v1.1 quasiment finalisée pour installation de la démo.
  • v1.1   correction des bugs remontés lors de la phase de recette de candid
  • POC_220115_CFB   Version stable au 220115
  • POC_v1   POC1 : Interrogation et affichage des données Les objectifs sont de : - Montrer les possibilités des technos que l'on a choisies. - Essuyer les plâtres point de vue partage et développement en équipe. - Mettre en place des solutions réutilisables pour la suite. Voici la premiere requête qui pourrait être implémentée : Pour les gènes BRCA1 et BRCA2, pour une serie donnée, récupérer l'ensemble des variants à +/- 50 pb autour des exons. La requête est paramètrable, via un formulaire. Les résultats seront affichés et téléchargeable au format Excel avec mise en forme. La requête est mise à disposition via une API. Pour le momment on ne s'occupe pas des gestions de droit. Ceci implique l'implémentation : 1 - Niveau base de données : Créer une ou des fonctions paramètrables pour faire remonter des données. 2 - Niveau application : Créer la couche pour pouvoir utiliser cette fonction et mettre a disposition les résultats aux vues. 3 - Interface utilisateur : Maquetter les vues le paramètrage (formulaire), l'affichage (beau tableau) et le téléchargement (fichier excel). puis les implémenter. 4 - Interface de programmation Créer la couche nécessaire pour la mise à disposition via une API web REST (affichage JSON).