hastie | A static site generator in Python

Provided

1. There is a unique solution (which should be true if your objective is regularized, which it appears to be by the last term.)
2. There are no bugs in either implementation.

Both implementations should return the exact same solution as the problem is a convex semidefinite program. The difference you should observe is

1. Runtime, one will likely run longer than the other, I would bet your implementation uses a general-purpose solver package (CVX) so should be slower.
2. Memory usage, once again, I would expect the general purpose (unutuned) package should consume more memory.
3. Numerical stability, in general this some implementations will be much more numerically stable. That is, if you use a weak regularization (very small lambda) you may find that some implementations fail to converge while others still work.

For small and toy problems this should not be a big deal (which is usually the case if you are an academic.) If you are a person trying to do something useful in the real world, runtime & memory usage tend to be extremely important, as they control what size problems you can tackle with your approach.

The only way to know the relative limitations to each approach is to implement and try both! At the very least, I would implement and run both approaches as a sanity check that both implementations are likely correct (the chance of both implementations being incorrect and reporting the same results across a range on inputs is very low.)

You will want to get your dataframe in "long" format to facilitate plotting. This is what's called Tidy Data and forms the basis for preparing data to be plotted using ggplot2.

The general idea here is that you need one column for the x value, one column for the y value, and one column to represent the value used for the tile color. There are lots of ways to do this (see melt(), pivot_longer()...), but I like to use tidyr::gather(). Since you're using rownames, instead of a column for gene, I'm first creating that as a column in your dataset.

First thing I would do is clean up the MATLAB API interface stuff. Remember that in Fortran you do not get automatic type promotion in function/subroutine argument lists like you do in C/C++. So it is important to get the signatures exact. You should NEVER be passing literal integers to MATLAB API functions. You should be passing variables that are typed exactly as the API specifies to ensure that there is not a mismatch. E.g., take this code:

The data is hosted at http://web.stanford.edu/~hastie/ElemStatLearn/datasets/ozone.data

The values are tab-separated, so you can read it using read_tsv from the readr package:

UICollectionView defaults to prefetchingEnabled == YES, which means that the collection view will request cells before it needs to display them. If the app's state changes such that the cells that have already been fetched need to be displayed differently, you can implement the collectionView:willDisplayCell:forItemAtIndexPath: method to update the cell.

It looks like this is exactly your problem... you turn on a feature that should change the way the cells look, but the cells that have been fetched but which aren't visible don't get updated. Implementing collectionView:willDisplayCell:forItemAtIndexPath: should solve the problem.