# DSCMRI Analysis parameter question

**URL:** https://discourse.slicer.org/t/dscmri-analysis-parameter-question/26519
**Category:** Support
**Created:** [November 30, 2022, 7:35pm UTC](https://discourse.slicer.org/t/dscmri-analysis-parameter-question/26519 "2022-11-30T19:35:47Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![mikebind](https://avatars.discourse-cdn.com/v4/letter/m/71e660/32.png) [@mikebind](https://discourse.slicer.org/u/mikebind)
#### Post date: [November 30, 2022, 7:35pm UTC](https://discourse.slicer.org/t/dscmri-analysis-parameter-question/26519/1 "2022-11-30T19:35:47Z")

</div>

We’re trying to use the DSCMRI Analysis module to calculate perfusion maps in Slicer, but are having trouble understanding some of the parameters and are getting unreasonable parameter map results. Three questions:

- What is the parameter “CBV/CBV Time Interval Value”? Perfusion processing parameter terminology seems to vary a lot from paper to paper, and we can’t figure out what this one means.
- Is there a sample perfusion imaging data set anyone is aware of where the parameter values are known that we can use to verify that we can get the right answers using this module and also play with to understand how the module parameters are affecting the results?
- Is the K2 parameter output the same as the “Ktrans” parameter sometimes reported in the literature, or is it different?

Thanks for any light you can shed on these questions!

---

<div class="post-metadata">

### Author: ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)
#### Post date: [November 30, 2022, 8:44pm UTC](https://discourse.slicer.org/t/dscmri-analysis-parameter-question/26519/2 "2022-11-30T20:44:56Z")

</div>

Have you checked in the source code if there is a description of thr algorithm or reference to a paper? Even if you find information on the algorithm it may still make sense to review the implementation to see exactly what is computed.
