Slutmonkey57b wrote: » That doesn't make any sense to normalise results on an aggregate basis. The whole point of individual achievement is its particular to the individual
Almost 8,000 Leaving Cert grades issued this year were higher than they should have been due to coding errors in the calculated grades process, according to new figures. In addition to Saturday’s announcement that 6,100 students received lower grades than they should have, the Department of Education confirmed on Sunday evening that about 7,943 grades were higher than they were supposed to be.
In this case, the Guardian understands, one lab had sent its daily test report to PHE in the form of a CSV file – the simplest possible database format, just a list of values separated by commas. That report was then loaded into Microsoft Excel, and the new tests at the bottom were added to the main database.
Capt'n Midnight wrote: » https://www.theguardian.com/politics/2020/oct/05/how-excel-may-have-caused-loss-of-16000-covid-tests-in-england
Wombatman wrote: » Awarding lower grades than should have been given only half the problem. While lower grades will be corrected upwards, higher grades awarded in error will not be corrected.
function getDisplayDuration(duration) { if (duration >= 60 * 60) { var d = new Date(duration * 1000); return ( addZero(d.getHours()) + "h " + addZero(d.getMinutes()) + "m " + addZero(d.getSeconds()) + "s" ); } else { var d = new Date(duration * 1000); return addZero(d.getMinutes()) + "m " + addZero(d.getSeconds()) + "s"; } function addZero(i) { if (i < 10) { i = "0" + i; } return i; } }
John_C wrote: » I found an entertaining bug today. It's a function to take in a duration in seconds and return a text string for display. For example getDisplayDuration(123) should return 02m 03s and getDisplayDuration(3723) should return 01h 02m 03s. Instead of working out the mathematics, the function converts the duration into a Date object, i.e. what time was it this number of seconds past midnight on 1st January 1970. It then reads the hours, minutes and seconds from that object. The end result is that (assuming you live in Ireland) the function produces the correct output during winter time but is off by an hour during daylight savings time.
John_C wrote: » The end result is that (assuming you live in Ireland) the function produces the correct output during winter time but is off by an hour during daylight savings time.
Idleater wrote: » I've seen a publishing schedule done by time of day, but specified by an arbitrary date. Basically "11:30 daily", but specified as "11:30 22 October 1950 ET".
dazberry wrote: » This reminds me of a place I worked where the empty/null/not supplied date for a customer dob was some arbitrary date in 1966. Caused a problem a few times
Wombatman wrote: » From the kind of developers that brought you 'We fooked up importing the German test results" and "We made a balls of the leaving cert standardisation process"..........https://arstechnica.com/tech-policy/2020/10/excel-glitch-may-have-caused-uk-to-underreport-covid-19-cases-by-15841/
Slutmonkey57b wrote: » Over a million rows in excel. I bet they went off and made dinner waiting for the thing to open.
sqlmonkey wrote: » ah yes - the old Excel Max Rows gotcha!
Buford T Justice wrote: » Access is (was) limited at 50MB
beauf wrote: » Because there's usually a mountain if VBA connected to it, you don't want to touch.
Capt'n Midnight wrote: » *shudders* Printout worked on a 386 but not on the 486 that replaced it There was a delay loop in the code. I increased the counter and left notes.
Seth Brundle wrote: » I'm fairly sure that the max size for an Access 97 database is 1GB. Access 2000 onwards is 2GB. I can recall seeing desktop applications using Access macros which were several hundred megs. I'm not saying it's perfect but it's not limited to 50Mb
beauf wrote: » Through lateral thinking I eventually got it to run in 24hrs.
Deleted User wrote: » You can't just leave us hanging. :pac: What did you do?