Converto | App for this guy who always forget to change the language

First, your Java generation of DH parameters is horribly wrong. The modulus (p) and generator (g) for DH are not simply large random primes. p must be a large prime, and does not need to be random, but MUST have a multiplicative group (Z_p^*) with 'non-smooth' order, that is the order's prime factorization must not consist entirely of small factors, or more concretely the order must have a large prime factor. Because the order of the multiplicative group for prime p is p-1, this is commonly accomplished by choosing a safe prime (p=2q+1) or a Schnorr prime (p=kq+1) where q is a sufficiently large prime. OTOH g need not be large (and MUST not be larger than or equal to p, which can happen with your code) and need not be random but must generate a subgroup of sufficient size (usually q). Choosing parameters as you did will sometimes fail outright (key agreement won't work) but most of the time will simply be insecure -- the shared value that was supposed to be secret can easily be determined by an adversary and used to expose and/or alter your supposedly secure data. I wonder if you or someone confused DH with RSA (or, less likely, Rabin) which is/are quite different, even though they all involve large numbers and mathematics.

But that's offtopic for SO. See wikipedia and numerous Qs and As on security.SX and crypto.SX. For your actual question:

It's the encoding. For (all) Java PublicKey objects, getEncoded() returns the 'SubjectPublicKeyInfo' format defined in X.509 (and more conveniently repeated in RFC5280 aka PKIX, linked there) which is based on ASN.1 and DER. In particular it contains an OID identifying the algorithm as DH, a parameters structure containing p and g, and the actual public key value (commonly notated y) wrapped in a BITSTRING; for the value you posted:

When you reference a variable in a FOR loop inside a batch script, you must use double %:

This is wrong:

Shapeless's Generic and LabelledGeneric are type classes that provide a generic representation for case classes and sealed trait hierarchies using hlists and coproducts. If you already have an hlist, you don't really need a Generic instance, and Shapeless doesn't provide one. In your case this means you can actually skip the genS and SR parts:

Those aren't ? characters. Those are two different unprintable characters that make up a Unicode byte order mark. You see ? because that's how the debugger, text editor, OS, or font in question renders unprintable characters.

To fix this, either change the output encoding, or use a character set on the other end that understands UTF-8. The former is a simpler fix, but the latter is probably better in the long run. Eventually you'll end up with data that needs an extended character.

Forcing fit_intercept=False is a huge constraint for the model, and you should be sure that you know exactly what you are doing before deciding to do so.

Fitting without an intercept in simple linear regression practically means that, when our single feature X is 0, the response Y should be also 0; here, it means that in the "year 0" (whatever that may mean), the Obesity should also be 0. Given that, the poor results reported are hardly a surprise (ML is not magic, and it is certainly implied that we do include realistic assumptions in our models).

It's not clear here why you have decided to do so, but I highly doubt it is what you intended to do. You should remove this unnecessary constraint from your model.

You just need to conditionally format the numbers, the same way you use different values for multiplier depending on the selected unit.

So you need to replace:

You could split at the space and use encodeURIComponent on the resulting array:

Since you're using -ExpandProperty, $t = $g[0].Group | Select -ExpandProperty Path stores (an array of) mere string values ([string] instances) in $t, namely the values of the .path properties on the input objects.

Select * reports the properties of those [string] instances (wrapped in [pscustomobject] instances), and given that strings only have one property - .Length - you'll see those length values only, not the strings' contents.

A simple example (reports the length of string 'one', i.e., 3):