pulsatrix
Loading...
Searching...
No Matches
search_space.hpp File Reference

Typed hyperparameter search-space description: named parameters, each continuous, log-uniform, integer, or categorical. More...

#include <cstdint>
#include <map>
#include <stdexcept>
#include <string>
#include <variant>
#include <vector>
Include dependency graph for search_space.hpp:
This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes

struct  pulsatrix::ParameterSpec
 One named parameter's description: its kind plus the bounds/categories that kind needs. Only the fields relevant to kind are meaningful (e.g. categories is empty/unused for Continuous) – this is a description, not a union, since a SearchSpace's own accessors (below) are the only place callers read it back. More...
 
class  pulsatrix::SearchSpace
 Describes a hyperparameter search space as an ordered list of named, typed parameters. Every HPO algorithm (grid/random search, GP-BO, TPE, Hyperband/ASHA) consumes a SearchSpace to know what it may propose; this type itself has no sampling logic (that is each algorithm's own job, e.g. RandomSample/GridSample). More...
 

Namespaces

namespace  pulsatrix
 

Typedefs

using pulsatrix::ConfigValue = std::variant< double, int64_t, std::string >
 A concrete value for one parameter – a double (Continuous/LogUniform), an int64_t (Integer), or a std::string (Categorical, naming one of that parameter's categories).
 
using pulsatrix::Configuration = std::map< std::string, ConfigValue >
 A concrete hyperparameter configuration: parameter name -> concrete value.
 

Enumerations

enum class  pulsatrix::ParameterKind { pulsatrix::Continuous , pulsatrix::LogUniform , pulsatrix::Integer , pulsatrix::Categorical }
 Which family of values a named parameter draws from. More...
 

Detailed Description

Typed hyperparameter search-space description: named parameters, each continuous, log-uniform, integer, or categorical.

Note
Recon (2026-09-27, campaign_exai_dl_library_hyperparameter_optimization activation): no SearchSpace/Trial/HPO type of any kind existed anywhere in this codebase before this mission – genuinely new, purely additive scaffolding, zero changes to Module/Tensor/DeviceBackend/MetricsSink.