Rob Egan

Hello, Apologies for the late reponse. This ticket arrived at the same time as an update from another and I didn't notice it. The icc_run.log has this error: *** Caught a fatal signal (proc 28): SIGILL(4) Which, in my experience, only happens when you build on 1 machine and execute on a different one. Your build platform must have the same CPU as the execute platform or else you run the risk that some optimization enabled in the build architechure cannot run on the execute architechure. So I suspect...

Hi sorry for the late reply. but this was a temporary problem that NERSC fixed a few weeks ago.

Hello NERSC is still working on a fix but set up a temporary solution so that you can proceed and download the test data from: https://portal-dev.nersc.gov/archive/home/r/regan/www/HipMer The easiest hack would be to edit hipmer_setup_ecoli_data.sh to use portal-dev.nersc.gov in the HIPMER_ECOLI_DATA_URL variable.

This is hosted at NERSC, and this happens a few hours per week when NERSC's tape system is down for maintenance, so generally waiting a few hours fixes it. HOWEVER today, there is a real problem with this service and I have opened a ticket with NERSC to have them fix it.

added another date format

modified for 2019 reports from kraken and lending club

modified for 2020 coinbase reports

Hello Sushma, Those warnings and errors are benign. The first "error: getstripe failed for" is something we should surpress. It attempted to set the lustre striping of your test directory, but, obviously, you do not have lustre, a parallel filesystem on your single node. The second warning: "UPC Runtime warning: Requested shared memory (2869 MB) > available (1984 MB) on node 0 (milanlogin): using 1984 MB per thread instead" Is informing you that HipMer requested 2869MB per rank of shared heap, but...