Closed vladimirg closed 7 years ago
Especially pronounced with ddRADseq data, but also an issue with WGS.
I have found a fix for this problem, the problem is the in versions prior to matlab R2014b under "nodisplay" matlab use Ghostscript to generate output instead of using the drivers built into MATLAB, as a result matlab uses the default DPI which is 72DPI. (more info) so we have two options:
Excellent! Let's try out the fix to make sure it works, but let's not deploy it yet - if lovelace is going to be updated soon anyway and they'll upgrade Matlab, then it should automatically solve our issue.
However, we do need to worry about the EPS issues we see on the newer Matlabs. Can you look into it, please?
I have checked and the EPS files work fine. As for the DPI changing the size in the QC environment did result in a better result, yet the file size is still lower then a file created in later versions of matlab (2014b and on). If the matlab version in lovelace will be updated it will solve the problem otherwise we can change the sizes of all of the figures according to the DPI.
Related to commit b2d55f18bf4ceb119e3d5604ce8c06b1107779f1, which adds support for Matlab 2016a.
Ymap's CNV bars in lovelace are too bold, and make the CNVs and the SNPs hard to read in the linear mode. This doesn't seem to happen on non-lovelace installations.
This was raised with Darren previously, transcript:
"There aren't any targeted configuration differences in the matlab installed on lovlace, but there potentially are differences in how matlab chooses its rendering engine based on hardware /software availability.
I had previously run into a really annoying error in relation to this. I had originally used some transparency features to construct the figures... but when matlab was running on the server (or in any console-only mode it turned out), it would crash hard any time it tried to use transparency in figures.
I bring this up because I wonder if it may be the root cause to the rendering issue you describe."