well-log-toolkit 0.1.136__tar.gz → 0.1.138__tar.gz

{well_log_toolkit-0.1.136 → well_log_toolkit-0.1.138}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: well-log-toolkit
-Version: 0.1.136
+Version: 0.1.138
 Summary: Fast LAS file processing with lazy loading and filtering for well log analysis
 Author-email: Kristian dF Kollsgård <kkollsg@gmail.com>
 License: MIT
@@ -1171,6 +1171,45 @@ plot = manager.Crossplot(
 plot.show()
 ```
 
+#### Multi-Layer Crossplots
+
+Combine different data types (Core vs Sidewall, different property pairs) in a single plot with automatic shape/color encoding:
+
+```python
+# Compare Core and Sidewall data with regression by well
+plot = manager.Crossplot(
+    layers={
+        "Core": ['CorePor', 'CorePerm'],
+        "Sidewall": ["SidewallPor", "SidewallPerm"]
+    },
+    color="Formation",              # Color by formation
+    shape="NetSand",                # Shape by net sand flag
+    regression_by_color="exponential-polynomial",  # Separate trend per formation
+    y_log=True,                     # Log scale for permeability
+    title="Core vs Sidewall Analysis"
+)
+plot.show()
+
+# Simpler version - automatic defaults
+manager.Crossplot(
+    layers={
+        "Core": ['CorePor', 'CorePerm'],
+        "Sidewall": ["SidewallPor", "SidewallPerm"]
+    },
+    y_log=True
+).show()
+# Automatically uses shape="label" (different markers per layer)
+# and color="well" (different colors per well)
+```
+
+**How it works:**
+
+- `layers` dict maps labels to [x, y] property pairs
+- Each layer gets combined in one plot with unified axes
+- Shape defaults to `"label"` (Core gets circles, Sidewall gets squares)
+- Color defaults to `"well"` for multi-well visualization
+- Perfect for comparing different measurement types (Core plugs vs Formation tests)
+
 ### Logarithmic Scales
 
 Perfect for permeability and resistivity data:

{well_log_toolkit-0.1.136 → well_log_toolkit-0.1.138}/README.md

@@ -1133,6 +1133,45 @@ plot = manager.Crossplot(
 plot.show()
 ```
 
+#### Multi-Layer Crossplots
+
+Combine different data types (Core vs Sidewall, different property pairs) in a single plot with automatic shape/color encoding:
+
+```python
+# Compare Core and Sidewall data with regression by well
+plot = manager.Crossplot(
+    layers={
+        "Core": ['CorePor', 'CorePerm'],
+        "Sidewall": ["SidewallPor", "SidewallPerm"]
+    },
+    color="Formation",              # Color by formation
+    shape="NetSand",                # Shape by net sand flag
+    regression_by_color="exponential-polynomial",  # Separate trend per formation
+    y_log=True,                     # Log scale for permeability
+    title="Core vs Sidewall Analysis"
+)
+plot.show()
+
+# Simpler version - automatic defaults
+manager.Crossplot(
+    layers={
+        "Core": ['CorePor', 'CorePerm'],
+        "Sidewall": ["SidewallPor", "SidewallPerm"]
+    },
+    y_log=True
+).show()
+# Automatically uses shape="label" (different markers per layer)
+# and color="well" (different colors per well)
+```
+
+**How it works:**
+
+- `layers` dict maps labels to [x, y] property pairs
+- Each layer gets combined in one plot with unified axes
+- Shape defaults to `"label"` (Core gets circles, Sidewall gets squares)
+- Color defaults to `"well"` for multi-well visualization
+- Perfect for comparing different measurement types (Core plugs vs Formation tests)
+
 ### Logarithmic Scales
 
 Perfect for permeability and resistivity data:

{well_log_toolkit-0.1.136 → well_log_toolkit-0.1.138}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "well-log-toolkit"
-version = "0.1.136"
+version = "0.1.138"
 description = "Fast LAS file processing with lazy loading and filtering for well log analysis"
 readme = "README.md"
 requires-python = ">=3.9"

{well_log_toolkit-0.1.136 → well_log_toolkit-0.1.138}/well_log_toolkit/manager.py

@@ -384,11 +384,18 @@ class _ManagerPropertyProxy:
 
     @labels.setter
     def labels(self, value: dict):
-        """Set labels for this property in all wells."""
+        """Set labels for this property in all wells.
+
+        Also sets property type to 'discrete' if not already set,
+        since labels are only meaningful for discrete properties.
+        """
         count = 0
         for well_name, well in self._manager._wells.items():
             try:
                 prop = well.get_property(self._property_name)
+                # Auto-set type to discrete if labels are being set
+                if prop.type != 'discrete':
+                    prop.type = 'discrete'
                 prop.labels = value
                 count += 1
             except (AttributeError, PropertyNotFoundError):
@@ -2481,37 +2488,52 @@ class WellDataManager:
         if well.name in self._name_mapping:
             del self._name_mapping[well.name]
 
+    def add_template(self, template: 'Template') -> None:
+        """
+        Store a template using its built-in name.
+
+        Parameters
+        ----------
+        template : Template
+            Template object (uses template.name as the key)
+
+        Examples
+        --------
+        >>> from well_log_toolkit import Template
+        >>>
+        >>> template = Template("reservoir")
+        >>> template.add_track(track_type="continuous", logs=[...])
+        >>> manager.add_template(template)  # Stored as "reservoir"
+        >>>
+        >>> # Use in WellView
+        >>> view = well.WellView(template="reservoir")
+        """
+        from .visualization import Template
+
+        if not isinstance(template, Template):
+            raise TypeError(f"template must be Template, got {type(template).__name__}")
+
+        self._templates[template.name] = template
+
     def set_template(self, name: str, template: Union['Template', dict]) -> None:
         """
-        Store a display template in the manager.
+        Store a template with a custom name (overrides template.name).
 
-        Templates can be referenced by name when creating WellView displays.
+        Use add_template() for the simpler case where the template's
+        built-in name should be used.
 
         Parameters
         ----------
         name : str
-            Template name for reference
+            Template name for reference (overrides template.name)
         template : Union[Template, dict]
             Template object or dictionary configuration
 
         Examples
         --------
-        >>> from well_log_toolkit.visualization import Template
-        >>>
-        >>> # Create and store template
+        >>> # Store with a different name than the template's built-in name
         >>> template = Template("reservoir")
-        >>> template.add_track(
-        ...     track_type="continuous",
-        ...     logs=[{"name": "GR", "x_range": [0, 150], "color": "green"}]
-        ... )
-        >>> manager.set_template("reservoir", template)
-        >>>
-        >>> # Use template in WellView
-        >>> from well_log_toolkit.visualization import WellView
-        >>> view = manager.well_36_7_5_A.WellView(
-        ...     depth_range=[2800, 3000],
-        ...     template="reservoir"
-        ... )
+        >>> manager.set_template("reservoir_v2", template)
         """
         from .visualization import Template
 

{well_log_toolkit-0.1.136 → well_log_toolkit-0.1.138}/well_log_toolkit/property.py

@@ -357,12 +357,18 @@ class Property(PropertyOperationsMixin):
         """
         Set the label mapping and mark source as modified.
 
+        Also sets property type to 'discrete' if not already set,
+        since labels are only meaningful for discrete properties.
+
         Parameters
         ----------
         value : Optional[dict[int, str]]
             Mapping of numeric values to label strings
         """
         if value != self._labels:
+            # Auto-set type to discrete if labels are being set
+            if value is not None and self._type != 'discrete':
+                self.type = 'discrete'  # Use setter to trigger value rounding
             self._labels = value
             self._mark_source_modified()
 

{well_log_toolkit-0.1.136 → well_log_toolkit-0.1.138}/well_log_toolkit.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: well-log-toolkit
-Version: 0.1.136
+Version: 0.1.138
 Summary: Fast LAS file processing with lazy loading and filtering for well log analysis
 Author-email: Kristian dF Kollsgård <kkollsg@gmail.com>
 License: MIT
@@ -1171,6 +1171,45 @@ plot = manager.Crossplot(
 plot.show()
 ```
 
+#### Multi-Layer Crossplots
+
+Combine different data types (Core vs Sidewall, different property pairs) in a single plot with automatic shape/color encoding:
+
+```python
+# Compare Core and Sidewall data with regression by well
+plot = manager.Crossplot(
+    layers={
+        "Core": ['CorePor', 'CorePerm'],
+        "Sidewall": ["SidewallPor", "SidewallPerm"]
+    },
+    color="Formation",              # Color by formation
+    shape="NetSand",                # Shape by net sand flag
+    regression_by_color="exponential-polynomial",  # Separate trend per formation
+    y_log=True,                     # Log scale for permeability
+    title="Core vs Sidewall Analysis"
+)
+plot.show()
+
+# Simpler version - automatic defaults
+manager.Crossplot(
+    layers={
+        "Core": ['CorePor', 'CorePerm'],
+        "Sidewall": ["SidewallPor", "SidewallPerm"]
+    },
+    y_log=True
+).show()
+# Automatically uses shape="label" (different markers per layer)
+# and color="well" (different colors per well)
+```
+
+**How it works:**
+
+- `layers` dict maps labels to [x, y] property pairs
+- Each layer gets combined in one plot with unified axes
+- Shape defaults to `"label"` (Core gets circles, Sidewall gets squares)
+- Color defaults to `"well"` for multi-well visualization
+- Perfect for comparing different measurement types (Core plugs vs Formation tests)
+
 ### Logarithmic Scales
 
 Perfect for permeability and resistivity data: