Commits on Source (63)
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alan Muñoz authored
-
Alan Muñoz authored
Merge pp dev See merge request aliby/aliby!17
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Arin Wongprommoon authored
WHY IS THIS CHANGE NEEDED?: - user needs to know these if they use the annotation script HOW DOES THE CHANGE SOLVE THE PROBLEM?: - edit docstring in top of file
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Alán Muñoz authored
-
Arin Wongprommoon authored
WHY IS THIS CHANGE NEEDED?: - detrend process overzealously removes columns if input dataframes have NaNs near the beginning or end. - this is because by default, df.dropna() uses how="any", i.e. it drops columns with at least one NaN HOW DOES THE CHANGE SOLVE THE PROBLEM?: - drops columns with at least one NaN is not the intention -- the intention is to remove column filled with NaNs created by rolling window operations. - so, specified the how argument WHAT SIDE EFFECTS DOES THIS CHANGE HAVE?: - i honestly don't know why i didn't catch it in the 1.5 years this process existed -- this seems so obvious. - this is a deprecated signal processing post-process (i use the butterworth filter instead), so i don't expect it to break things much EVIDENCE THAT COMMIT WORKS:
-
Arin Wongprommoon authored
-
Arin Wongprommoon authored
-
Arin Wongprommoon authored
WHY IS THIS CHANGE NEEDED?: - crosscorr process does not have stationary option and therefore will not perform calculations correctly if all signals are in-phase. HOW DOES THE CHANGE SOLVE THE PROBLEM?: - Additional 'stationary' parameter that tells the process to compute the mean over replicates AND time points. WHAT SIDE EFFECTS DOES THIS CHANGE HAVE?: - crosscorr process not used anywhere else in aliby, so should not affect aliby. - crosscorr process used in multiple places in skeletons (particularly arin's projects). this is an *additional* parameter, and the existing behaviour of crosscorr process is same as stationary=False, so i don't expect breaking changes. EVIDENCE THAT COMMIT WORKS: - new test to be run REFERENCES: - #72
-
Arin Wongprommoon authored
WHY IS THIS CHANGE NEEDED?: - https://gitlab.com/aliby/aliby/-/jobs/4743945774 complains "UnboundLocalError: local variable 'trace_B' referenced before assignment". - i had forgotten the case where trace_B is defined
-
Arin Wongprommoon authored
-
Arin Wongprommoon authored
feat(postproc): crosscorr has stationary option See merge request aliby/aliby!18
Showing
- .gitlab/issue_templates/bug.md 24 additions, 2 deletions.gitlab/issue_templates/bug.md
- README.md 15 additions, 8 deletionsREADME.md
- docs/source/INSTALL.md 42 additions, 0 deletionsdocs/source/INSTALL.md
- docs/source/index.rst 0 additions, 1 deletiondocs/source/index.rst
- docs/source/specifications/io_dependencies.org 16 additions, 0 deletionsdocs/source/specifications/io_dependencies.org
- examples/parsers/swainlab_logfile_header_example.log 123 additions, 0 deletionsexamples/parsers/swainlab_logfile_header_example.log
- poetry.lock 1364 additions, 1054 deletionspoetry.lock
- pyproject.toml 18 additions, 12 deletionspyproject.toml
- src/agora/abc.py 7 additions, 7 deletionssrc/agora/abc.py
- src/agora/io/bridge.py 4 additions, 1 deletionsrc/agora/io/bridge.py
- src/agora/io/cells.py 3 additions, 3 deletionssrc/agora/io/cells.py
- src/agora/io/metadata.py 5 additions, 5 deletionssrc/agora/io/metadata.py
- src/agora/io/signal.py 34 additions, 21 deletionssrc/agora/io/signal.py
- src/agora/io/writer.py 12 additions, 16 deletionssrc/agora/io/writer.py
- src/agora/utils/association.py 0 additions, 120 deletionssrc/agora/utils/association.py
- src/agora/utils/cast.py 1 addition, 1 deletionsrc/agora/utils/cast.py
- src/agora/utils/indexing.py 152 additions, 0 deletionssrc/agora/utils/indexing.py
- src/agora/utils/kymograph.py 69 additions, 1 deletionsrc/agora/utils/kymograph.py
- src/agora/utils/merge.py 90 additions, 7 deletionssrc/agora/utils/merge.py
- src/aliby/baby_client.py 10 additions, 4 deletionssrc/aliby/baby_client.py
Source diff could not be displayed: it is too large. Options to address this: view the blob.
src/agora/utils/indexing.py
0 → 100644