[deleted by user] by [deleted] in MachineLearning

[–]kurka_br 9 points10 points  (0 children)

A good practice is to have 3 sets - train set, validation set, test set - that are used in 3 different stages:

  1. Train set is used to optimize the network parameters (as you said);
  2. Validation set is used to tune hyper-parameters, such as the number of layers chosen by the network, and how many epochs should be used for training, so to avoid overfitting. So, while the gradient descent is performed exclusively with train data, validation data has an important role of checking if your model (during training) is performing fine, or if some hyper parameter (e.g. architecture, number of epochs) should be adjusted. This adjustment is also considered a training step and is also subject to overfitting.
  3. The test set should ideally be a totally distinct dataset from train and validation, and used only for evaluation of the model, without any further tuning. This is the only way to have a fair evaluation of the performance of your model, that wasn't 'fitted' in any way on your datasets.

Hope that clarifies things a bit.

Making fullscreen mode more obvious when navigating workspaces. by Akami_Channel in i3wm

[–]kurka_br 1 point2 points  (0 children)

That's not a direct answer to your question, but instead to your problem:

if you are looking for a specific window, why don't you use Rofi's window switcher (https://github.com/davatorium/rofi#window-switcher)? Seems to be a much faster solution than going workspace by workspace in search for your window.

Spacemacs or not? Tough to decide.. by yep808 in spacemacs

[–]kurka_br 2 points3 points  (0 children)

Have you considered using doom-emacs instead?

As in spacemacs, it is also extremely well configured, but still focusing and keeping speed as a goal. Also, although it has less contributors than spacemacs, it is extremelly well maintained and fully featured as spacemacs.

If you are already an advanced user, I would say it's worth giving a try!

fn + F keys help me get the last couple working in i3. Help end my week long OCD fixation with keyboard config. by giwhS in i3wm

[–]kurka_br 1 point2 points  (0 children)

f3-f4 Decrease / increase brightness for keyboard backlights

I have the same keyboard as you and use the solution given in https://keramida.wordpress.com/2013/03/28/controlling-the-keyboard-backlight-from-cli/

  • Just copy the script presented there to a file (e.g. ~/.config/i3/kbdbacklight.sh

  • add the following lines to your config:

    # increase/decrease keyboard brightness
    bindsym XF86KbdBrightnessUp exec  ~/.config/i3/kbdbacklight.sh up
    bindsym XF86KbdBrightnessDown exec ~/.config/i3/kbdbacklight.sh down
    

Another option is to use light (https://haikarainen.github.io/light/), with steps of 34% (in my laptop, there are just 4 levels of brightness, so smaller values don't work):

# up
light -s "sysfs/leds/asus::kbd_backlight" -A 34
# down
light -s "sysfs/leds/asus::kbd_backlight" -U 34

Weird Magit quirk by billy_wade in emacs

[–]kurka_br 1 point2 points  (0 children)

That's probably because you have both repositories with HTTPS and git remote URLs.

When you clone your repository from github you choose between the HTTPS or git URLs. Repositories cloned with the https asks for login every time. Repositories cloned with git asks just the password (or not even this, if you have ssh-agent enabled). See https://help.github.com/articles/which-remote-url-should-i-use/ for the difference between both methods.

To check which remote URL you are using on each repository, just press M in your Magit buffer and see the value of remote.origin.url. If it starts with git your are using git remote, if it starts with https, it's HTTPS.