Jose Daniel Lara

@copilot add a constant with the supported eltypes in the vector inputs to communicate to the user which types are supported in the vector and in the second error mention...

@copilot in addition to the current method in `transform_array_for_hdf method` add a check in the the constructor for `Deterministic` in the file deterministic.jl that checks for the supported types in...

@copilot implement is_transform_array_for_hdf_supported using multiple dispatch returning true for the supported types and false for any other, that is a more Julian way to do it than a long list...

agree you can open a PR with this

working with @daniel-thom on this. We think there is an issue with the axis definitions in these functions for `IncrementalPiecewiseLinearBreakpointParameter`. This function ```Julia function _additional_axes( ::OptimizationContainer, ::IncrementalPiecewiseLinearBreakpointParameter, devices::U, ::DeviceModel{D, W},...

@GabrielKS the code here is causing some dimensionality mismatch. I am not sure how to change the code to avoid this problem with the `expand_ixs` code ```Julia function expand_ixs(ixs::Tuple, dest::AbstractArray)...

@daniel-thom I reassigned this because it is in the same path to resolve #1170

This function can disappear with this fix 

Store the time series attributes in the time series, parameter attributes object to avoid having to do this.

closing as duplicate of #1150