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

[Cornerstone adapters] Tool is undefined when saving FreehandRoi tool in structured report #306

Closed
SveinungOverland opened this issue Sep 12, 2022 · 4 comments
Labels

Comments

@SveinungOverland
Copy link
Contributor

static getTID300RepresentationArguments(/*tool*/) {
const { handles, finding, findingSites, cachedStats = {} } = tool;

Hey, we use DCMjs to create structured reports from cornerstone and cornerstone-tools (not the new cornerstone3d).
For the most part this seems to work just fine, but we recently wanted to add FreehandRoi tooling to the reports. This never seemed to work as tool was always undefined when saving the report. Upon further examination the code seems to work just fine if tool is put into the argument list.
The question is really just, why is tool commented out? The function seems to work just fine with it in, and not work at all without it.

@pieper
Copy link
Collaborator

pieper commented Sep 12, 2022

@wayfarer3130
Copy link
Contributor

@SveinungOverland - I'm not sure why it was commented out - it shouldn't have been, but for that class I was just updating it to match the format of the other ones, without having a full configuration that enabled it to run. Please create a PR with it added back end, testing both save and restore.

@SveinungOverland
Copy link
Contributor Author

@wayfarer3130 - I created the PR, but from what I can see dcmjs seems to be missing a testing structure for adapters and I don't think I should be the one to create it. So if you know of anyone more familiar with dcmjs and js testing I would appreciate if you tag them here.

@pieper pieper closed this as completed in feeb532 Oct 10, 2022
@github-actions
Copy link

🎉 This issue has been resolved in version 0.28.2 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants