Skip to content

ENH: tracking changes to ML manuscript (la-2026-00306e) #26

@adamwitmer

Description

@adamwitmer

This issue is to be used to track changes associated with review comments from the manuscript la-2026-00306e, specifically those having to deal with improvements related to questions about the machine-learning (some review comments have been omitted here because Mihee will address them separately).

Reviewer 1:

  • Systems that may have irregular shaped droplets or precipitates and droplets present: Peacock et al. [https://doi.org/10.1021/acsami.0c21036] describes some mixtures where the system is immiscible but does not necessarily form clearly visible droplets. Some of the systems formed with highly branched polysaccharides, led to structures observed by brightfield microscopy that would be interesting to test the performance on. For example, the system formed from chondroitin sulfate and hydroxypropyl cellulose (see text for others). A simple demonstration that the approach works with systems like these to detect the presence of liquid-liquid phase separation would be a great addition.
  • Effect of microscope resolution: It is mentioned in the text but not explored. How well the system works as a function of image resolution would be relatively easy to characterize and useful for a user when selecting a microscope system. It would also be great to see what would come out of a super resolution system, e.g., super-resolution dark field microscopy or phase-contrast super resolution if these microscopy systems are available.
  • The effect of temperature: An easy to perform and useful demonstration would be to detect the transition from one phase to two phases, starting with a miscible composition and gradually lowering the temperature to the point where droplets become detectable, then raising the temperature again. It might even be possible to observe hysteresis in this experiment if temperature of the solution can be reliably recorded.

Most of the above have to do with performing analysis of additional images provided by Mihee

Reviewer 2

  • For each feature, please plot their distributions in the SI, partitioned into each class (two phase vs one phase) to see if there are meaningful patterns we can spot with our eyes. I imagine that a simple rule based on the number and size of bubbles could suffice instead of the machine learning model. This will help us see which features tend to separate the class more. Or you can make a pairplot in seaborn where it shows the relationship between the features and color/shape the points according to class. I just think more insights into your data are needed. The feature importance study is helpful. I was going to suggest that but see you have it.
  • Spell out how many training images you have in the Methods. Are they for one ATPS i.e. with fixed components? Do they span the whole space of concentrations of the two components? How did you choose the concentrations for the training examples? Clarify/explain in the text. Do the training images come for all depths and all positions? Can the same model see images at different depths (it doesn’t matter, does it?). What is the class balance? If the classes are imbalanced, area under precision-recall curve more appropriate than AUROC.
  • Do you train one independent ML model per ATPS (i.e. for two given components) or does one ML model handle looking for ATPSs for ANY two components (polymers/salts)?
  • In Figure 5 were these images included in the train set? State if so or if not. If so this is not a proper test/train split to evaluate the ML model. The ability of ML model to evaluate if an ATPS is present should be best on test images it didn’t see during training. It is unclear if you are following these standard and required practices of test/train splits/cross validation for the ML.
  • Do you expect the classifier to transfer from one ATPS to another? Or for each ATPS you must train a model? Clarify in the text.
  • Please concretely list the features input to the ML model in the text. E.g. “spatial distribution patterns” is very vague.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions