Git Product home page Git Product logo

Comments (11)

luiztauffer avatar luiztauffer commented on June 19, 2024

For some reason we have assumed before that the default was 70-150 Hz.
I changes it now to 70-200 Hz

from ecogvis.

jessierliu avatar jessierliu commented on June 19, 2024

@luiztauffer Indeed the default should be 70-150Hz (this is the classic definition of high gamma). All I was saying is to have the option to add bands that are already defined.

Currently, if you want to add a new band to the high gamma calculation, you have to enter the center and sigma frequencies yourself. So I'd like there to be the other pre-defined bands (as defined in https://github.com/luiztauffer/process_ecog/blob/docker/ecog/utils/bands.py), available.

As a specific example, I'd imagine you click the High Gamma button and you want to create a new high gamma file. The default bands 70-150 Hz are already selected, and greyed out are the other Chang Lab frequency bands. Perhaps each band has a checkbox next to them? So if I wanted to then include up to 200Hz, I could just select those extra few bands. Let me know if that make sense!

from ecogvis.

luiztauffer avatar luiztauffer commented on June 19, 2024

The changes are in place, let me know if that's what you had in mind!

from ecogvis.

jessierliu avatar jessierliu commented on June 19, 2024

The dialog box looks great, this is exactly what I had in mind!

However, when I try to make the new file, I get this error:

Screen Shot 2019-06-26 at 6 04 23 PM

We previously discussed that invalid times have to be stored as a separate .csv file. Do you know why it needs to reference this table? In the new nwb file that I'm working off of, there is no invalid times table. I could make an empty one if need be.

from ecogvis.

luiztauffer avatar luiztauffer commented on June 19, 2024

Oops, I should be testing for the existence of this group (and other things, I just came to realize). Thanks for pointing that out!

from ecogvis.

luiztauffer avatar luiztauffer commented on June 19, 2024

Ok, I corrected for this and some other fields present in the files @bendichter provided me with.
The main problem we're having now is when creating new files, but preserving fields from another file without being connected to them. This is an open Issue at NeurodataWithoutBorders/pynwb#668
The current implementation should work temporarily, but it's important to note that's not the best way and we should change it to use the option link_data=False once it's working on pyNWB.

from ecogvis.

jessierliu avatar jessierliu commented on June 19, 2024

Ah, okay. The high gamma button works properly now for me. So is it linking the data right now? That is, the relative paths must be maintained between the new high gamma file and the original raw file?

from ecogvis.

luiztauffer avatar luiztauffer commented on June 19, 2024

No, the way it's done right now there's no link. You can move your files around and test it! Let me know if anything is failing

from ecogvis.

jessierliu avatar jessierliu commented on June 19, 2024

Okay, so right now, everything gets copied into the new files? Having the raw+preprocessed files and the high gamma files be independent is, I think, our goal? Do you think there's a reason for it not to be? Perhaps I'm not grasping what you mean exactly, by how this isn't the best way to do this.

from ecogvis.

luiztauffer avatar luiztauffer commented on June 19, 2024

The way it is implemented right now, you have two options:
1 - High Gamma is saved in current file (the one with raw/preprocessed)
2 - High Gamma is saved in a new file, of user's choice. In this file, some other data will be copied as well, such as electrodes, lab name, stimulus... but not 'raw' or 'preprocessed' data. This new file should work independently of the original file.

from ecogvis.

jessierliu avatar jessierliu commented on June 19, 2024

Right, and option 2 is what I envision most people doing. Thanks for clarifying!

from ecogvis.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.