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

Sizing prediction for split-plot and unpaired study #91

Open
qigongFDA opened this issue Mar 2, 2016 · 8 comments
Open

Sizing prediction for split-plot and unpaired study #91

qigongFDA opened this issue Mar 2, 2016 · 8 comments
Assignees
Labels

Comments

@qigongFDA
Copy link
Contributor

We should provide split-plot and unpaired study option in Sizing part.

The Main problem is the BDG_coefficient derivation.

@qigongFDA
Copy link
Contributor Author

  1. Create new method genBDGSplitUnpairedCoeff in DBRecord.java
  2. Enable "study design" in size panel.
  3. Preliminary check split-plot result between iRoemetz and iMRMC.
    There is one problem.
    In iRoemetz numerical analysis, we set BDGbias=BDG (BDRecord 726 line).

@qigongFDA
Copy link
Contributor Author

Add study Design to Explore Experiment Size.

@qigongFDA
Copy link
Contributor Author

iRometz should not have Not fully data loaded warning and not export sim-comp files

@brandon-gallas
Copy link
Member

Regarding the export of sim-comp files, I don't believe the related code has any value and should be deleted. If you agree, delete that code. If you think otherwise, let me know.

@qigongFDA
Copy link
Contributor Author

qigongFDA commented Mar 15, 2016

We could use swarm command to run iRoeMetz validation parallel on linux. (i.e. swarm doValidation.txt)

There are two things we need to pay attention:

  1. We should run swarm in perceus but not login to one of the node.
  2. The txt file should in following format:
    export DISPLAY=":0.0"; java -jar iRoeMetz.jar /raidb/qigong/imrmc/001.irm
    As our iRoeMetz has gui (we just don't display it in validation), and some node might not connect to a screen, we need to set a number to DISPLAY. Otherwise, system will give us this error.
    "No X11 DISPLAY variable was set, but this program performed an operation which requires it."

@qigongFDA
Copy link
Contributor Author

I think we could close this issue

@brandon-gallas
Copy link
Member

I want you to document how to run iRoeMetz in parallel. When ready, I will try and run iRoeMetz in parallel following the documentation (no one-on-one help from you). Then we can work together to improve the documentation and ultimately close this issue.

@brandon-gallas
Copy link
Member

Sorry @qigongFDA .
I thought this was an issue related to the iRoeMetz workflow. I am going to move my last comment over to #81
This issue is the sizing analysis in iMRMC.
We have already merged this work into the iMRMC master branch, and we could close this issue.
HOWEVER

  1. These new features of iMRMC need to be adequately discussed in documentation.
  2. I would like to wait until we are happy with the validation results.

Let's keep this issue open until those steps happen. Then we will create a new version with the new sizing options.

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

2 participants