Implement aggressive G-code cleaning post-processing for Cosmos3D printer

[Copilot]

• Implement aggressive G-code cleaning for Cosmos3D printers
• Remove content before "COSMOS" marker
• Modify layer change markers (;LAYER_CHANGE → ;LAYER_CHANGE M3)
• Remove comment lines and M73 progress commands
• Filter G1 commands (remove E values, keep X/Y coordinates, skip Z-only and F-only lines)
• Add consecutive dot filtering (remove G1 commands with X/Y closer than 1.5mm)
• Update documentation with new filtering logic
• Test the new filtering logic with sample G-code

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[PolGuixe]

@copilot

The script in python would be this one:

def clean_gcode(input_file, output_file):
    """
    Cleans a G-code file by applying the following rules:
    - Removes all lines before the "COSMOS" marker
    - Keeps layer change markers (;LAYER_CHANGE)
    - Removes other lines with comments (starting with semicolon)
    - Removes lines with M73 commands
    - Removes G1 lines that only contain Z movements (with or without F parameter)
    - Removes G1 lines that only contain F (feed rate) parameter
    - Keeps all G1 lines that contain X or Y coordinates
    - Removes E values from G1 commands while keeping the rest of the line

    Args:
        input_file (str): Path to the input G-code file
        output_file (str): Path to save the cleaned G-code file
    """
    with open(input_file, 'r') as file:
        lines = file.readlines()

    cleaned_lines = []
    keep_processing = False  # Flag to start processing after "COSMOS" marker

    for line in lines:
        stripped_line = line.strip()

        # Start processing only after the "COSMOS" marker
        if "COSMOS" in stripped_line:
            keep_processing = True
            continue

        if not keep_processing:
            continue

        # Keep layer change markers
        if stripped_line == ";LAYER_CHANGE":
            cleaned_lines.append(";LAYER_CHANGE M3\n")
            continue

        # Skip other comment lines (starting with semicolon)
        if stripped_line.startswith(";"):
            continue

        # Skip progress update commands (M73)
        if "M73" in stripped_line:
            continue

        # Process G1 movement commands
        if stripped_line.startswith("G1"):
            # Remove extruder (E) values but keep the rest of the line
            cleaned_line = re.sub(r'\sE[-+]?[0-9]*\.?[0-9]+', '', stripped_line)
            
            # Keep any line that has X or Y coordinates
            if 'X' in cleaned_line or 'Y' in cleaned_line:
                cleaned_lines.append(cleaned_line + '\n')
                continue
            
            # Skip lines that only have Z movement (with optional F parameter)
            if re.match(r'^G1\s+Z[-+]?[0-9]*\.?[0-9]+(?:\s+F[-+]?[0-9]*\.?[0-9]+)?$', cleaned_line):
                continue
            
            # Skip lines that only have feed rate (F parameter)
            if re.match(r'^G1\s+F[-+]?[0-9]*\.?[0-9]+$', cleaned_line):
                continue
            
            cleaned_lines.append(cleaned_line + '\n')

    # Write the cleaned G-code to the output file
    with open(output_file, 'w') as file:
        file.writelines(cleaned_lines)

regarding the files generated, do we need to create a machine, a process and new filaments?

[Copilot]

@copilot

The script in python would be this one:
...

Thanks for sharing the Python script! I can see it implements a more aggressive G-code cleaning algorithm compared to the current embedded C++ implementation.

Current Implementation Status:

The Cosmos3D printer profiles are already fully configured with:

✅ Machine: "Cosmos3D X1" and "Cosmos3D X1 60 nozzle"
✅ Process: "Concrete Printing @COSMOS3D X1 60 nozzle"
✅ Filaments: "fdm_filament_concrete" and "Generic Concrete"

Current vs. Your Algorithm:

The embedded C++ post-processing currently adds optimization comments and display messages, while your Python script performs content removal/filtering:

• Current: Adds identification comments, print section markers, layer change notifications
• Your script: Removes content before "COSMOS" marker, strips comments, removes E values, filters G1 commands

Options to proceed:

1. Replace the current embedded processing with your algorithm (converted to C++)
2. Enhance the current processing to include your cleaning rules
3. Keep both - current for basic optimization, yours for advanced cleaning

Would you like me to implement your Python algorithm as embedded C++ code to replace or complement the current implementation? The cleaning approach you've described would be more aligned with specialized concrete printing workflows.

Commit: f7ab8b9

[PolGuixe]

@copilot please proceed with option 1.

[Copilot]

@copilot please proceed with option 1.

I've implemented Option 1 as requested - replaced the current embedded processing with your Python algorithm converted to C++.

The new implementation performs aggressive G-code cleaning:

• Removes all content before "COSMOS" marker
• Modifies layer change markers (;LAYER_CHANGE → ;LAYER_CHANGE M3)
• Removes all comment lines and M73 progress commands
• Filters G1 commands: removes E values, keeps X/Y coordinates, skips Z-only and F-only lines
• Preserves other commands (M104, M106, M84, etc.)

Tested with sample G-code and confirmed the algorithm matches your Python script's behavior exactly.

Commit: da1d9b6

Warning

Firewall rules blocked me from connecting to one or more addresses

I tried to connect to the following addresses, but was blocked by firewall rules:

• esm.ubuntu.com
  • Triggering command: /usr/lib/apt/methods/https (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[PolGuixe]

@copilot why we need this files for this task?

resources/profiles/Cosmos3D/filament/Cosmos3D Generic PLA.json
resources/profiles/Cosmos3D/machine/Cosmos3D.json
resources/profiles/Cosmos3D/process/0.20mm Standard @Cosmos3D.json
resources/profiles/Cosmos3D/process/fdm_process_cosmos_common.json

[Copilot]

@copilot why we need this files for this task?

resources/profiles/Cosmos3D/filament/Cosmos3D Generic PLA.json
...

You're absolutely right to question these files. They aren't actually needed for the G-code post-processing task.

The post-processing algorithm works by checking if any printer's printer_model config contains "Cosmos" - it doesn't require specific profile files to exist. The cleaning algorithm will automatically run for any printer configured with "Cosmos" in its model name.

These profile files (machine, process, filament) were added in an earlier commit but aren't essential for the core post-processing functionality. The G-code cleaning works independently of these configurations.

Would you like me to remove these unnecessary profile files since they're not required for the post-processing feature?

[PolGuixe]

@copilot yes, remove the unnecessary files

[Copilot]

@copilot yes, remove the unnecessary files

Removed all unnecessary Cosmos3D profile files. The post-processing algorithm only needs to check for "Cosmos" in the printer_model configuration and doesn't depend on any specific profile definitions.

Commit: 40b75b7

[PolGuixe]

@copilot will the last changes make the post processing still work?

In the last commit I have only removed the files that you have originally added that I don't think are required

[Copilot]

@copilot will the last changes make the post processing still work?

In the last commit I have only removed the files that you have originally added that I don't think are required

Yes, the post-processing will still work perfectly after removing those profile files.

The Cosmos3D post-processing algorithm only requires:

• The printer_model configuration to contain "Cosmos" (which comes from any printer profile)
• Access to the G-code file

It does NOT depend on the specific Cosmos3D profile files that were removed. The detection logic simply checks:

const auto *printer_model = config.opt<ConfigOptionString>("printer_model");
if (!printer_model || printer_model->value.find("Cosmos") == std::string::npos)
    return false;

So any printer profile (even user-created ones) with "Cosmos" in the model name will trigger the post-processing. The removed files were indeed unnecessary for the core functionality.

[PolGuixe]

@copilot can you modify the postprocessing script that you have generated so it is able to clean and remove the GCODE instructions that are consetive dots that are closer than 1.5 mm?

[Copilot]

@copilot can you modify the postprocessing script that you have generated so it is able to clean and remove the GCODE instructions that are consetive dots that are closer than 1.5 mm?

I've modified the post-processing script to filter out consecutive G1 commands where the X/Y coordinates are closer than 1.5mm to the previous point. The algorithm now:

1. Tracks the last X and Y position
2. Calculates the Euclidean distance between consecutive points
3. Only keeps G1 commands with X/Y that are at least 1.5mm away from the previous point

For example:

• Point at (0,0) → kept (first point)
• Point at (1,0) → filtered (1.0mm < 1.5mm)
• Point at (3,0) → kept (3.0mm ≥ 1.5mm)
• Point at (10.5,10.3) after (10,10) → filtered (0.58mm < 1.5mm)

The documentation has been updated with the new filtering logic and example transformations.

Commit: da0a4c7