Move gpmix module from ego to moe crate

[Copilot]

Relocates mixed-integer GP mixture functionality from egobox-ego to egobox-moe where surrogate modeling logically resides.

Changes

In egobox-moe:

• Added gpmix/ module containing:
  • types.rs: XType enum (Float, Int, Ord, Enum variable types) and discrete() helper
  • mixint.rs: Mixed-integer GP mixture implementation with continuous relaxation (~933 lines)
  • Public API: MixintGpMixture, MixintGpMixtureParams, as_continuous_limits(), to_discrete_space(), to_continuous_space()
• Made struct fields and training methods public for ego integration

In egobox-ego:

• Removed XType definition and gpmix/mixint.rs (~1035 lines deleted)
• gpmix/mod.rs now re-exports moe types and implements SurrogateBuilder trait for GpMixtureParams and MixintGpMixtureParams
• Updated imports across 8 files to reference egobox_moe::XType
• Backward compatibility maintained via re-exports

Example

// Before: XType was defined in ego
use egobox_ego::XType;

// After: XType comes from moe, ego re-exports it
use egobox_ego::XType;  // Still works
use egobox_moe::XType;  // Also works

The SurrogateBuilder trait implementation remains in ego to connect moe's surrogate types to ego's optimizer, preserving the dependency direction (ego depends on moe, not vice versa).

Original prompt

Start implementation

The user has attached the following file paths as relevant context:

• .github\copilot-instructions.md

[Chronological Review: The conversation began with the user requesting to move the `egobox_ego::gp_mix` module to `egobox_moe`. The user then corrected the module name from `gp_mix` to `gpmix`. Following this, the user requested to start the implementation of the move.]

[Intent Mapping:

• User Request 1: "I would like to move egobox_ego::gp_mix module in egobox_moe."
• User Request 2: "gpmix not gp_mix" (clarification on the module name).
• User Request 3: "Start implementation" (indicating readiness to begin the coding process).]

[Technical Inventory:

• Module: egobox_ego::gpmix (the module intended for relocation).
• Target: egobox_moe (the new location for the module).]

[Code Archaeology:

• Current File: mixint.rs located at d:\rlafage\workspace\egobox\crates\ego\src\gpmix\.
• No specific code changes have been documented yet as the user is preparing to start the implementation.]

[Progress Assessment:

• Completed Tasks: None yet, as the user has only outlined the intention to move the module and clarified the name.
• Partially Complete Work: The user is ready to start the implementation of the move.]

[Context Validation: All necessary context for continuing the work on moving the gpmix module to egobox_moe is captured.]

[Recent Commands Analysis:

• Last Agent Commands: The user issued commands to clarify the module name and to initiate the implementation.
• Tool Results Summary: No tool results were generated as the conversation focused on user requests and clarifications.
• Pre-Summary State: The agent was actively preparing to start the implementation of moving the gpmix module when the token budget was exceeded.
• Operation Context: The commands were executed to clarify the user's intent and to begin the coding process for the module relocation.]

1. Conversation Overview: - Primary Objectives: - "I would like to move egobox_ego::gp_mix module in egobox_moe." - "gpmix not gp_mix" (clarification on the module name). - "Start implementation" (indicating readiness to begin the coding process). - Session Context: The user is focused on relocating the `gpmix` module from `egobox_ego` to `egobox_moe` and has clarified the correct module name. - User Intent Evolution: The user initially requested the move, corrected the module name, and expressed readiness to start the implementation.

2. Technical Foundation:

• Module: egobox_ego::gpmix (the module intended for relocation).
• Target: egobox_moe (the new location for the module).

3. Codebase Status:

• File Name: mixint.rs
  • Purpose: Contains the implementation details for the gpmix module.
  • Current State: No modifications have been made yet as the user is preparing to start the implementation.
  • Key Code Segments: Not applicable yet as no changes have been documented.
  • Dependencies: This module is part of the egobox_ego crate and will need to be integrated into egobox_moe.

4. Problem Resolution:

• Issues Encountered: None reported yet.
• Solutions Implemented: None yet, as the user is in the planning phase.
• Debugging Context: No ongoing troubleshooting efforts as the user has not started implementation.
• Lessons Learned: No insights have been documented yet.

5. Progress Tracking:

• Completed Tasks: None yet.
• Partially Complete Work: The user is ready to start the implementation of the module move.
• Validated Outcomes: No features or code have been confirmed working through testing.

6. Active Work State:

• Current Focus: The user is preparing to implement the move of the gpmix module.
• Recent Context: The last few exchanges involved clarifying the module name and readiness to start implementation.
• Working Code: No specific code snippets have been modified or discussed recently.
• Immediate Context: The user is set to begin the implementation of moving the gpmix module.

7. Recent Operations:

• Last Agent Commands: User commands to clarify the module name and to initiate the implementation.
• Tool Results Summary: No tool results were generated as the conversation focused on user requests and clarifications.
• Pre-Summary State: The agent was actively preparing to start the implementation of moving the gpmix module.
• Operation Context: The commands were executed to clarify the user's intent and to begin the coding process for the module relocation.

8. Continuation Plan:

• Pending Task 1: Start the implementation of moving the gpmix module to egobox_moe.
• Pending Task 2: Ensure all dependencies and references to the module are updated accordingly.
• Priority Information: The immediate next step is to begin coding the relocation of the module.
• Next Action: "Start implementation" is the immediate next step to be taken by the user.

Created from VS Code.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.