-
-
Notifications
You must be signed in to change notification settings - Fork 229
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
BUG: AttributeError: module 'pymc' has no attribute 'diagnostics' #205
Comments
|
Additional information on how I installed the packages from Anaconda CMD.exe Prompt: Finally, I have tried to use both gelman_rubin(models) and hddm.analyze.gelman_rubin(models). Both fails with the same error stating Thank you. |
I transferred this to the pymc2 repo, but I don't think you'll have much luck. Can you upgrade to HSSM? |
Hello Thomas, Thank you for your message and I understand that pymc (2.3.7) is an old package/version, so unlikely to get support. I have submitted my issue with the Stop Signal Go tasks in the thread lnccbrown/HSSM#324 As for the Stroop task, I cannot seem to get similar values of v and a as those from HDDM. This gives me the 2 drift rates (one each for the congruent and incongruent conditions) and the boundary separation for each participant. I input data from all participants together, using the subj_idx column to identify the participants. In HSSM, the code I used to try to get the output for one participant is as follows: However, the output doesn't always converge (RHat > 1.1), and I sometimes have to run multiple iterations to make sure it converges. The estimated parameters are not close enough to those from HDDM to give me confidence. To try to run multiple participants' data together (combining participants' data and adding the subj_idx column to identify the participants), I used the following code: The output from the above HSSM code indicates non-convergence (RHat much above 1.1) and the parameters are not at all similar to those from HDDM. As for Go/NoGo, I am not sure if HSSM will handle the -999 rt value for successful withholding of a nogo trial. I also am not sure what the HSSM syntax would be for the equivalent of HDDM syntax: m=hddm.HDDMStimCoding(mydata,depends_on={'v':'condition'},include='z', stim_col='condition',split_param='z', Can you help me with getting the correct equivalent HSSM syntax for the 3 tasks so I can transition from HDDM to HSSM with my study? Or should I open up new query/bug in the HSSM Github page for my Stroop and Go/NoGo queries above? Many thanks for your time. |
Yes, best to move this to HSSM. |
Describe the issue:
I have been running Gelman Rubin convergence tests after running the HDDM function. and they were working fine up until 13th October 2023. I have in the last week tried to run the same script again in Jupyter Notebook (from Anaconda) and after the HDDM iterations are complete, the Gelman Rubin test fails, citing the reason as "AttributeError: module 'pymc' has not attribute 'diagnostics'. I have not changed the code or the python environment. I have however updated the Anaconda software version recently, but not sure if this would have had an effect.
I have tried to rebuild the python environment multiple times, and compared the packages list/versions, but I can't see anything has changed.
The reason I am using an older version of Python and pymc is because they are compatible with HDDM 0.8.0.
I have attached the conda list to show the packages and versions in the python environment.
hddm conda list.docx
Reproduceable code example:
Error message:
PyMC version information:
I have attached the conda list below.
hddm conda list.docx
Context for the issue:
I am using HDDM to estimate parameters for three tasks (Stroop, Go/NoGo and Stop Signal tasks), and needs to use the Gelman-Rubin convergence test to ensure the parameter estimation iterations converge. As the Gelman-Rubin test was working up until mid-October, I am relying on it to ensure my experiment analysis can be completed. I do not know of any other way to do the Gelman-Rubin test without using the pymc package. Any ideas why this error occurs now (and not before), and what I can do to work around it? Thank you.
The text was updated successfully, but these errors were encountered: