highMemorySolver

[RuiminYan]

I cannot find the highMemorySolver link. Could you give a one? Thank you! You did a GREAT job!

[or18]

Thank you for your kind words!

The HighMemorySolver does not have a standalone page; it can be accessed through the main 3x3x3 solver. By selecting F2L, LL Substeps, LL, or LL AUF from the Solver dropdown menu, you can utilize the HighMemorySolver functionality.

Additionally, options labeled “Lite” (e.g., LL Lite) are lightweight versions that significantly reduce memory usage compared to the HighMemorySolver. In most cases, these lightweight solvers are sufficient. If you find that the search speed is not sufficient, you can use the HighMemorySolver or make it easier to find solutions by reducing the search space through the Advanced Settings by setting move order restrictions or move count limits.

If you have any further questions or need assistance, please feel free to reach out!

[RuiminYan]

Thanks! Actually I am currently working on the simulation of distributions of fixed color/dual color/cn xxcross,xxxcross, and I only use the Analyze feature. I use almost 1,000,000 333/333oh/333fm/333ft/333bf scrambles from WCA website. Here is my code for batch solver https://github.com/RuiminYan/CubeRoot/blob/master/batch%20cross%20solver.js
and demo https://youtu.be/GM6YibNv1bI

But on my Alienware m17 R4 laptop, it cost too much time to get the stat of a single scramble (around 4~5 seconds) which is much slower than my iPhone 15 Pro Max (less than 2 seconds).

btw, may I ask what is your WCAID (or name)?

[or18]

That's an interesting simulation!
However, the cross analyzer available on my website is based on the F2L Lite solver and performs database calculations each time, so I don't think it's suitable for such batch calculations. The database calculation will only be performed once if you remove the Emscripten code from src/crossAnalyzer/analyzer.cpp and run it locally. However, due to the slow search speed of the XXXCross solver in Lite Solver, such large-scale calculations are expected to take a considerable amount of time.

Therefore, I think it would be best to create a cross-analyzer program in C++ based on the highMemorySolver's F2L solver, though I cannot say how much faster the calculations will be.

Unfortunately, I have never participated in official competitions, so I do not currently have a WCAID.

For the analyzer based on the highMemory F2L solver, I'll try to create it if I have time.

[RuiminYan]

I am running 12 Chrome tabs (locally) at once and I can get the data of 2 scrambles per second which is decent for me. Hopefully I can get the data of all wca scrambles by the end of the year.

Could you make xxcross trainer and xcross+free pair trainer? They are very helpful for top cubers. xxxxcross analyzer may be good as well though it's time-consuming.

btw I find a bug. Currently, the shadow of white and grey sticker is the same dark grey so we cannot differentiate them.

[or18]

Thank you for pointing out the bug. Regarding the sticker mask bug, I've fixed it in the previous commit, and the shadow of the gray ignored sticker now appears transparent.

For xxcross and xcross+free pair trainers, it may be possible to create trainers with up to 8-9 moves selectable.

[RuiminYan]

Thank you! I am trying to automate clicking the "Analyze" button using a JavaScript snippet in the browser console.

1. when I chose F2L Lite or F2L, the analyzer button was actually clicked since there was a table showing up.
2. when I chose other solvers (e.g. Pairing), the analyzer button was not actually clicked since there was not a table showing up.

demo here: https://youtu.be/nd5ObmoGxgw

js code here:

(function() {
    // 1. Locate the Analyze button
    // Iterate through all <button> elements to find the one whose innerText contains "analy" (case-insensitive).
    const analyzeBtn = [...document.querySelectorAll("button")]
        .find(b => b.innerText.toLowerCase().includes("analy"));

    if (analyzeBtn) {
        // 2. Click the button
        analyzeBtn.click();
        console.log("✅ Analyze button clicked successfully.");
    } else {
        // 3. Error handling
        console.error("❌ Analyze button not found on the page. Please ensure the website is fully loaded.");
    }
})();

[or18]

I found that all "Analyze" buttons for each solver were detected by the code; however, only the first button was clicked using analyzeBtn.click();.

2. when I chose other solvers (e.g. Pairing), the analyzer button was not actually clicked since there was not a table showing up.

Regarding this behavior, the "Analyze" button for F2L Lite or the F2L solver has actually been pressed.

So I open all Analyzer <details> elements and locate the Analyze button within any details that are not hidden. The sample script is as follows:

(function() {
    // 1. Locate all details elements with "analyze" in their id and open them
    const detailsElements = document.querySelectorAll("details[id*='analyze']"); // Filter details with "analyze" in the id
    detailsElements.forEach(details => {
        if (!details.open) {
            details.open = true; // Open the <details> element
            console.log("Opened details element with ID:", details.id);
        }
    });

    // 2. Locate all buttons
    const analyzeBtns = [...document.querySelectorAll("button")]
        .filter(b => 
            b.innerText.toLowerCase().includes("analy") && 
            !b.classList.contains("hidden") && 
            !isInsideHiddenDetails(b) // Check if it is inside a hidden details element
        );

    // 3. Extract their ids
    const analyzeBtnIds = analyzeBtns.map(btn => btn.id).filter(id => id); 

    // 4. Output the ids to the console
    console.log("Detected Visible Analyze Button IDs:", analyzeBtnIds);

    // 5. Click each detected button
    analyzeBtns.forEach(btn => {
        btn.click(); // Click the button
        console.log(`✅ Analyze button clicked: ${btn.id}`);
    });

    // 6. Function to check if a button is inside a hidden details element
    function isInsideHiddenDetails(button) {
        let parent = button.closest('details');
        return parent && parent.classList.contains('hidden'); // Check if it has the hidden class
    }
})();