Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve documentation of physio setups #277

Open
tsalo opened this issue Jul 24, 2020 · 1 comment
Open

Improve documentation of physio setups #277

tsalo opened this issue Jul 24, 2020 · 1 comment
Labels
Documentation This issue or PR is about the documentation

Comments

@tsalo
Copy link
Member

tsalo commented Jul 24, 2020

Detailed Description

Currently, there is some information about common setups in the Best Practices page. However, I think it would be very helpful to (1) get more specific about different overall setups and their strengths/weaknesses, (2) reorganize the documentation to distinguish the general setup and modality-specific hardware, and (3) maybe add basic diagrams. Diagrams would be a bit of work, but I think they'd be very helpful for new folks.

Tagging @CesarCaballeroGaudes @smoia @RayStick @sangfrois.

Context / Motivation

When FIU first started working on installing BioPac, none of us knew that you could have a T-splitter to directly send the trigger signal from the scanner to both the task computer and the physio computer, so we ultimately chose to feed the existing trigger signal going to the task computer through to the physio computer via a parallel port and using our task scripts. We only learned recently how that was suboptimal.

The phys2bids site is a great opportunity to provide all of the documentation necessary to at least know what questions new folks should be asking their scanner or physio hardware support teams. Information about costs would also help folks figure out what the best solution is for their facility, based on their current hardware and budget.

Possible Implementation

Not so much an "implementation" as a list of things I think we should cover:

  • Break down general hardware by scanner manufacturer and physio manufacturer
  • Break down modality-specific hardware, possibly by physio manufacturer
    • Model IDs and links to product pages would definitely help people in their searches
  • Break down consumables by modality (e.g., gels and electrodes for EDA, nasal cannula for CO2 if not using a mask).
  • Include estimated costs for everything we can estimate costs for
  • Describe common trigger setups, possibly with diagrams (or pictures) and definitely with lists of pros and cons:
    • Have a T-splitter to split the trigger signal from the scanner to output to both the task computer and the physio computer.
      • This may require a custom circuit to extend the duration of the trigger pulse so that it can be reliably captured by BioPac.
    • Manually add a marker in the physio software when the scan starts.
    • Connect the task computer to the physio computer through a parallel port and have your task scripts send a signal when they are started by the trigger signal from the scanner.
    • Multi-run vs. single-run
@tsalo tsalo added the Documentation This issue or PR is about the documentation label Jul 24, 2020
@smoia smoia added this to the phys2bids second semester 2020 milestone Jul 30, 2020
@vinferrer vinferrer added Urgent If you don't know where to start, start here! and removed Urgent If you don't know where to start, start here! labels Sep 10, 2020
@RayStick
Copy link
Member

RayStick commented Oct 8, 2020

I think this is a great initiative. It will take time to cover all this, and summarize it well, so I won't promise to do that anytime soon, but I've flagged this as something I can contribute to.

@RayStick RayStick self-assigned this Oct 8, 2020
@RayStick RayStick removed their assignment May 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation This issue or PR is about the documentation
Projects
None yet
Development

No branches or pull requests

4 participants