Seems the Alerce Broker might need an update.

@KKruszynska has documented her research in:

• Add ALeRCE broker LCOGT/mop#234

• Form fields out of date
  Compare with ALeRCE ZTF Explorer

  • Modify Classification Filters

    • Modify Light Curve Class classes:
      In TOM Toolkit:
      

      In ALeRCE:
      

    • Add classifier: Lc Classifier Top

    • Add classifier: Lc Classifier BHRF Forced Phot

    • Add classifier: LC Classifier ATAT Forced Phot Beta

    • Add classifier: Stamp Classifier 2025 Beta

      In ALeRCE:
      

• Add The Number of Detections Range Filter

  • Min
  • Max
    In ALeRCE:
    

• Modify Other Parameters
  In TOM Toolkit:
  

  • Ranging field no longer present in ALeRCE
  • Detections Lower is now a part of the Number of Detections Filter

• General Filters:

  • Remove Mean Right Ascension
  • Remove Mean Declination
  • Add Delta MJD (days)

  In TOM Toolkit:
  

  

  In ALeRCE:

• Functionality that should be added
  • Fetch classification for an alert for a selected classifier
  • Some functionality that would allow the user to grab features provided by a classifier.

Materials:

• Notes from a meeting with Alejandra Aranciba-Munoz about Microlensing in ALeRCE
• Notebook prepared by ALeRCE developers on using ALeRCE API to access events classified as microlensing and relevant features
• Important note from ALeRCE developers:

New classifiers started on May 29 2025 (lc_classifier_BHRF_forced_phot) and June 3 2025 (LC_classifier_ATAT_forced_phot(beta)). Given the 2min timeout for public users, this query to the object table is useful before querying the probability table, specially for classifiers in beta mode. Note that light curve classifiers in a beta stage lack some indices (ranking and probability) in the probability table, making some queries very slow.