Open isomemo opened 1 year ago
@mgross @arunge
Problem 1 is solved (had lower/upper case difference in naming proxies).
@mgross Could you help with the 2nd point here, or give more details on what exactly should be added (e.g. screenshots)? If the model must be adjusted for this, I could first implement the UI such that you only would have to update the model afterwards. (If it's only a simple change, please just tell me where the new inputs must be added.)
@mgross You can wait on this! I will write a fix (not only to the reported issue) using pseudo code. Should have this ready tomorrow.
@isomemo: I don't understand the second issue, should this be implemented again? A long time ago it was implemented that way (correlation between sources), but we changed it to correlation between proxies because of your request
"MVN for table sources.
@mgross I did not do a good job of explaining it. It is not the correlation between sources. It is the correlation among proxies but by source instead of a common matrix for all sources as per the mathematical descriptions and as in FRUITS. This is why I mentioned each table within Sources (meaning the table for each source). I am preparing a file with a detailed pseudo-code description.
@mgross @arunge
Please give top priority to solving this over any other task!
Check this file: model test correlation.zip
Two problems
1) The proxies for the sources are correlated. I tried both repeated measurements and direct values entry options but in both cases, I get an error message that the number of proxy dimensions is wrong
2) Option missing to assign var-covar values for each source. Assuming that this may also be missing when using the repeated measurements option.