| ... | ... | @@ -2,8 +2,10 @@ |
|
|
|
title: Simple Radiomics Workflow
|
|
|
|
---
|
|
|
|
|
|
|
|
## Name
|
|
|
|
Simple Radiomics Workflow
|
|
|
|
|
|
|
|
|
|
|
|
## Description
|
|
|
|
This example creates a Hero Imaging workflow that extracts radiomic features from CT scan image of a patient diagnosed with soft-tissue sarcoma. This radiomics workflow is created using the following Imaging nodes
|
|
|
|
|
|
|
|
| Node name | Workflow Purpose|
|
| ... | ... | @@ -15,9 +17,22 @@ This example creates a Hero Imaging workflow that extracts radiomic features fro |
|
|
|
| Export to .csv | | Exports the extracted radiomics features to .csv file for storage or further data analysis |
|
|
|
|
| Visualize | Visualises the interpolated image and intensity mask.
|
|
|
|
|
|
|
|
## Visuals
|
|
|
|
|
|
|
|
|
|
|
|
**Hero Imaging Files**
|
|
|
|
## Installation
|
|
|
|
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
|
|
|
|
- [Database file](url)
|
|
|
|
- [Workflow file](url)
|
|
|
|
|
|
|
|
## Usage
|
|
|
|
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
|
|
|
|
|
|
|
|
|
|
|
|
## Authors and acknowledgment
|
|
|
|
Show your appreciation to those who have contributed to the project.
|
|
|
|
|
|
|
|
## License
|
|
|
|
For open source projects, say how it is licensed.
|
|
|
|
|
|
|
|
|
