It would be far more practical if ratings would use [1-5] keys and 1-5 filter would use [shift+number]. Basically the other way around than currently is.

Why? Because you only have to filter once in a while while assigning 1-5 stars is a job done every time there's a new image. Pressing shift and numbers is awkward and not that fast.

If I want to change the settings (for example to use the Dogecoin Mainnet), I need to manually enter #settings in the URL.

The pthreads based multi-threading code should be improved (IMHO). I see two options:

1. keep the internal 'explicit' interface more or less like it is but switch from pthreads to c++11 threads.
2. remove the 'explicit' interface, which should simplify the code significantly and switch to OpenMP where applicable.

I would strongly prefer the second option as is would reduce the complexity of

Two screenshots, could not get image saving to work. One is MLV App 1.3 (should be same as 1.4), other is 1.5 - the new one is a bit less sharp, sharpening for both was set at 60 (same MASXML)

![screenshot from 2019-02-03 23-25-28](https://user-images.git

@aiff22 Hi，
I try to train with my own data, but when level1 and level0, the MS-SSIM loss be Nan (actually MS-SSIM loss is not used at level1).
So I run the training code in debug mode, I found that, in some case, the SSIM could be negative.
I found the code of MS-SSIM implements at jorge-pessoa/pytorch-msssim and discussions about this problem

The web ui on mobile devices could be improved.

• Burger menu to show/hide left menu items
• A way to show right sidebar for images (and hide it again)
• Navigation in fullscreen (exit, move left/right) see also #36

The default image extension mode used in scipy.ndimage.convolve is 'reflect', which reflects the image about the edge of the pixels. This introduces artefacts in the edge of the resulting RGB layers when demosaicing:

# Constant ones as image
orig = np.ones((2,2)) 
R, G, B 

Provide better information about the format and increments of data. Current documentation is not as clear as it could be.

Example:
Data at 10nm gives the following error.
Please double check the Camera Sensitivity data (e.g. the increment should be uniform from 380nm to 780nm).
This error message does not make it clear that the data must be 5nm increments. In fact, it implies that data at

At the first image of the icon view, when you mouse-over the thumb to get the info tooltip, it is trying to draw it half outside the screen and it only flickers without showing properly.

Workaround: If you hover on the next image and get the tool, and then move to hover the first image, the info is visible. edit: Second workaround: hover the thumb lower, eg. on top of the filename.

Ubuntu 15.1