Heiko Strathmann

But we should still add the typemap -- even the build now has a workaround Typemap force @vigsterkr @sperka

Typemap force @vigsterkr @sperka

We currently have a workaround that avoids problems with this, but still would be good to fix

Yes contributions are welcome here. Let us know if you need help. Reading existing codes, examples, and the gp book by Rasmussen is probably the best start

Check the code for the other embeddings (the converters ported from tapkee). This is probably a bit more tricky than the other entrance tasks we have.

That seems a bug, thanks for reporting. Just to confirm, you run **the above code** ? Because the error message seems to have other things in it?

Thanks. I just realised the strings you put are uninitialized. Is that maybe cause of the error?

- I would actually go to move all GP parameters to log-domain. We can still interface and store them in standard domain, but all dervatives in log-domain would be better...

I usually prefer general solutions that do things automatically to those that require extra arugments and thinking by the user. Users should not be able to decide whether a parameter...

I guess we cannot avoid the fact that Shogun developers have to specify the range of parameters when registering them. Therefore, I would go for _optional_ lower and upper bound...