Closed GidonFrischkorn closed 4 months ago
Cool, thanks, I'll take a look now :)
I have now committed an updated version of the files addressing most of your comments. We should definately look into the issue with loading the files that I saved. On my machine I get no error messages and all the loaded objects have the class bmmfit
. Maybe we need to have a look if the file
option interacts with some other environment info that breaks portability between different setups.
I have now committed an updated version of the files addressing most of your comments. We should definately look into the issue with loading the files that I saved. On my machine I get no error messages and all the loaded objects have the class
bmmfit
. Maybe we need to have a look if thefile
option interacts with some other environment info that breaks portability between different setups.
there shouldn't be a problem with the file option - both you and I when we run the models fresh we save the correct object. I suspect you might have uploaded some old fits to osf. Can you reupload your current fit objects after you confirm they are all bmmfits?
Just as a short update. I will run the examples over the weekend with v0.5.3
and then upload the new results files to OSF. I will sent you a notification once thats done, so that you can then check if all the files load correctly for you too.
I now updated the .rds
files on OSF and ran all models with the newest bmm
version. Now, with downloading the new saved bmmfits
the error when loading them should no longer appear. I also addressed your other comments.
Looks good and I can confirm all the bmm files now work for me as well. Is this ready to merge or have you done any changes in the last few weeks you might want to incorporate?
This pull request contains the updated examples using the current
bmm
version. Prior to merging this into themaster
branch, we should consider creating a tag to allow users to access the scripts associated with the initialbmm
release. In the long run this will likely be less relevant, but during the review process, I think it could be nice to be able to quickly switch back and forth between the different iterations of the Tutorial scripts.In this pull request: