Hello, from the explanation
Recall that hierarchical mapping maps the cell 100 times, using a random subset of marker genes for each iteration, and assigning the cell to the cell type that is most correlated with the cell in the plurality of those 100 iterations. bootstrapping_probability is the fraction of the 100 iterations that chose the final assignment"
in this example I was able to infer that the number of bootstrap iterations used for the web portal is 100 and then confirmed this by finding the section at the bottom of the downloaded output .json that notes the config and type assignment values.
Could the default bootstrap iterations be noted on the web portal page to make that key value clearer to users? Additionally, could the config section of the results be moved to a separate file to make them easier to find/review for users who might not be familiar with the format or expect those values to be reported in that file along with the per cell outputs? I understand that the code base is used for both the command line and web portal options and the command line option makes the config values very clear since they are defined upfront by the user but for documentation/reproducibility of the web version it would be helpful to have those values reported in a way that's easier to find.
Hello, from the explanation
in this example I was able to infer that the number of bootstrap iterations used for the web portal is 100 and then confirmed this by finding the section at the bottom of the downloaded output .json that notes the config and type assignment values.
Could the default bootstrap iterations be noted on the web portal page to make that key value clearer to users? Additionally, could the config section of the results be moved to a separate file to make them easier to find/review for users who might not be familiar with the format or expect those values to be reported in that file along with the per cell outputs? I understand that the code base is used for both the command line and web portal options and the command line option makes the config values very clear since they are defined upfront by the user but for documentation/reproducibility of the web version it would be helpful to have those values reported in a way that's easier to find.