Closed jeffa5 closed 2 years ago
650c43e6b788d094677b6ef75c7d26a292d3eb00/ecdf.jpg 650c43e6b788d094677b6ef75c7d26a292d3eb00/scatter.jpg 650c43e6b788d094677b6ef75c7d26a292d3eb00/throughput.jpg
Available from here
416746472e88d761ec407d47375a04c519dc4ba9/ecdf.jpg
416746472e88d761ec407d47375a04c519dc4ba9/scatter.jpg
416746472e88d761ec407d47375a04c519dc4ba9/throughput.jpg
Available from here
Available from here
Available from here
Have you consider @achamayou's suggestion of using a blob store instead?
Have you consider @achamayou's suggestion of using a blob store instead?
Yeah, would probably need some help setting that up. Was also considering git lfs as it keeps it repo-oriented.
It is up to you but I would suggest sticking with this for now as it already works (although the throughput graph doesn't seem to have any data) and create a ticket to switch to blob storage/gitlfs before the repo gets too large
Available from here
I think this is ok for now and once merged we can look at improving it some more
throughput graph doesn't seem to have any data?
Available from here
throughput graph doesn't seem to have any data?
Think I've fixed that now, was due to a 0 rate causing / 0
error
Available from here
Available from here
@heidihoward should be ready to go now, including throughput data!
Can you put othervars somewhere else and just show the variable which changes in the legend? They are quite long, and they will likely on get longer 😜
Can you put othervars somewhere else and just show the variable which changes in the legend? They are quite long, and they will likely on get longer 😜
Yes, worked out the variable ones and only made them on the legend, kept the invariant ones as a title
Available from here
Available from here