Uploaded image for project: 'The Virtual Brain'
  1. The Virtual Brain
  2. TVB-2747 Implement Import / Export of PSE
  3. TVB-2813

Correct VM create date to fix the import in PostgreSQL

    XMLWordPrintable

Details

    • Sub-task
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • 2.0.10
    • None
    • None
    • VBC Sprint 9
    • 8.2 Pipeline Integration

    Description

      There is an incompatibility with PostgreSQL at PSE import time because of how we generate the create_date for view models involved in a PSE.

      E.g.: We instantiate the SimulatorAdapterModel once and generate the create_date in the constructor. Then we use that SimulatorAdapterModel for each operation in PSE and write it to H5 with the same create_date for all operations. At import time, we sort the operations by this create_date, and it will be the same for all operations in a PSE. The problem is that BurstConfiguration should be imported before any of the PSE results. As we keep it only in the first operation folder, we should ensure that one is imported first.

      My first thought is to generate the create_date at H5 write-time. 

      Gliffy Diagrams

        Attachments

          Activity

            People

              paula.popa Paula Prodan
              paula.popa Paula Prodan
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 1 day Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 1 day, 2 hours, 30 minutes
                  1d 2h 30m