Hey there! That warning is telling you to swap the integer dimension argument for the VectorType enum—this makes your code clearer and avoids ambiguity, plus it’s the supported approach going forward. Let’s walk through how to fix this properly.

Why the Integer Argument is Obsolete #

The old integer parameter was vague: did 1 mean you wanted to broadcast the vector as rows or columns? The VectorType enum removes that confusion by explicitly defining whether your N×1 vector should be treated as a column vector (broadcast across all columns of the matrix) or row vector (broadcast across all rows).

The Updated, Non-Obsolete Code #

Assuming your original int = 1 meant you wanted to add the column vector to every column of your N×D matrix (the most common use case for an N×1 vector), here’s the correct replacement:

var result = Elementwise.Add(M, v, VectorType.Column);

If you ever needed to treat a vector as a row (for example, adding a 1×D vector to every row), you’d use:

var result = Elementwise.Add(M, rowVector, VectorType.Row);

Quick Additional Notes #

• If you’re using the MathNet.Numerics library (the most common source of Elementwise.Add), make sure you have these using directives:

  using MathNet.Numerics.LinearAlgebra;
  using MathNet.Numerics.LinearAlgebra.Double;
  

• Using VectorType makes your intent explicit for both the compiler and other developers reading your code, which boosts maintainability.
• This overload is the long-term supported version, so you won’t have to worry about it being removed in future library updates.

内容的提问来源于stack exchange，提问作者Jie Hu