The MWM is a multiscale multiplicative data model which is able to capture not only correlation structure but also `spikiness . Here, it is shown in comparison with a multiscale additive model which can match only the correlations
SHOW FULL COLUMNS FROM `jrk_downrecords` [ RunTime:0.002444s ]
SELECT `a`.`aid`,`a`.`title`,`a`.`create_time`,`m`.`username` FROM `jrk_downrecords` `a` INNER JOIN `jrk_member` `m` ON `a`.`uid`=`m`.`id` WHERE `a`.`status` = 1 GROUP BY `a`.`aid` ORDER BY `a`.`create_time` DESC LIMIT 10 [ RunTime:0.091699s ]
SHOW FULL COLUMNS FROM `jrk_tagrecords` [ RunTime:0.002576s ]
SELECT * FROM `jrk_tagrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 20 [ RunTime:0.002238s ]
SHOW FULL COLUMNS FROM `jrk_member` [ RunTime:0.002268s ]
SELECT `id`,`username`,`userhead`,`usertime` FROM `jrk_member` WHERE `status` = 1 ORDER BY `usertime` DESC LIMIT 10 [ RunTime:0.003922s ]
SHOW FULL COLUMNS FROM `jrk_searchrecords` [ RunTime:0.002254s ]
SELECT * FROM `jrk_searchrecords` WHERE `status` = 1 ORDER BY `num` DESC LIMIT 5 [ RunTime:0.003584s ]
SELECT aid,title,count(aid) as c FROM `jrk_downrecords` GROUP BY `aid` ORDER BY `c` DESC LIMIT 10 [ RunTime:0.015906s ]
SHOW FULL COLUMNS FROM `jrk_articles` [ RunTime:0.002694s ]
UPDATE `jrk_articles` SET `hits` = 1 WHERE `id` = 194442 [ RunTime:0.001364s ]
