Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
I io_trc
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tju-uba
  • io_trc
  • Issues
  • #2

Closed
Open
Created Oct 30, 2018 by Tomas Pastore@tpastoreOwner

Bug in TRC writer?

I converted the 449_correct.edf to TRC with trcio writer and import it from brain quick. This info can be visualized opening 449_correct.TRC exam and doing click on the top left icon in Brain Quick window. bugImportTRC

Perhaps it is not so important for the demo, but check that the strings of dates, for instance: the recording start, can't that be affecting event detection? I will try printing that in python with the trc reader meanwhile.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking