Closed pcream closed 4 months ago
Ok, I've found that I can prevent the error from occurring by adjusting the seed number up (2 to 3/4). Not sure why that happens, or how that might impact results, but I assume it is ok if there is a burn-in period.
The second index error is related to not having a proposal_step_sigma with enough "terms" to run with more clones than the default 4. Again, not sure how that effects the run by having more than 4.
I have had some trouble getting certain data to run through fitclone for unknown reasons. I can get the .tsv/.yaml labeled "NMS_bottleneck_A" to run perfectly fine and it outputs reasonable fitness values given the clonal composition. But if I alter some of the percentages of certain clones as in "NMS_bottleneck_D" (without changing clone number/timepoints), suddenly I get a failure related to NaN's during an interation of OutterPGAS. It's not clear what's causing this, I have also tried other clonal compositions varying in number and frequency and have had other errors related to index errors. Really unsure what could be causing these errors and why changes in frequency would break the the whole pipeline.
Many thanks!
NMS_bottleneck_D.txt NMS_bottleneck_D_yaml.txt NMS_bottleneck_A.txt NMS_bottleneck_A_yaml.txt