# User Portlet

Sjoerd Smit
Discussions
This definitely looks useful. I do have one bit of feedback: you expose the functions setDateOrderToDayMonthYear and setDateOrderToMonthDayYear and hide the variable workingDateOrder that they influence. That's fine by itself, but in that case...
If you're having trouble reading in Chinese characters, I recommend fiddling about with the character encoding. I had a similar problem once that I solve by first setting: \$CharacterEncoding = "UTF8" Give that a try before importing the...
You don't need to write out the definition of the sigmoid yourself. You can just use the built-in function LogisticSigmoid. With FunctionExpand you can transform it into the Exp form if you want: FunctionExpand[l*LogisticSigmoid[k (x -...
I think it depends on how you do your GP regression in this case and what kernel you use. If you make a point estimate for the covariance length scale, I think you end up with constant prediction variance far from your data (since basically none of...
As for your second question: > In addition, to associate x coordinates (given by the data vector Xdata) to each residue vector, I use Timeseries like this res360 = TimeSeries[residu360, {Xdata}] >But isn't there another way of...
I think the function Complement will be of use to you.
I know I'm a bit late to this party, but for anyone who still has the same question in 2019: I wrote a repository functions specifically for this: [KullbackLeiblerDivergence on the Wolfram Function Repository][1]. It should work for all sorts of...
Hi Daniel, Yes, that should be not problem at all. data should be either an n by 3 matrix or a list of rules of the form {{x11, x21} -> y1, ... }. From there it should work without issue, though you may need to re-scale the data if your xi...
If you include the a=2 definition in the Initialization and set SaveDefinitions -> True, it should work, I think. Unfortunately I don't have time right now to give a better explanation than that, but I hope it works. You can always try to make...
I completely agree with this. Personally, I think that something along the lines of Haskell-style lazy lists fits best with WL's paradigms. In the past I did an exercise to try an implement this [from scratch][1], though I'm aware that similar...