Jump to content

Recommended Posts

Posted
I found the trick was to ensure sims is not open i.e use the discover login directly..takes a lot less resource..

 

A good tip, but not ideal when you're trying to compare data!

 

On a seperate note...does anyone know what the parameters of the attendance timeline are i.e cumulative or weekly calculated.

 

It's cumulative based on the current academic year (based on the date, not what is set in SIMS academic management). Also, all data applies to on roll students in the current academic year - which means that any exams analysis must be done within the two weeks before next term starts. Both major limiting factors in my opinion, but apparently there are already plans to make this more flexible

 

On a final note..discover presented to 20 schools so far.. 95% take up rate..especially useful on identifying behavioural issues by category and location..i.e bullying.

 

I've personally found the dynamic groups to be Discover's most powerful feature so far for this purpose

Posted
It's a joke because c2d covers a rather large range of cpu's, go back and try using one of the old low end 1.8ghz c2d or one of the laptop 1.2ghz ones, there's a massive difference between those and a c2d

 

Your getting CoreDuo and Core2Duo mixed up. C2D run Discover ok, even the old ones.

 

you think silvershite will be around in a few years? MS seem to be dropping it like a hot potato in favour of HTML5/javascript to keep up with Apple/Google. I'm sure Capita will happily pass on the redevelopment costs to schools for the next (low system requirement, platform independent, browser based) version.

 

Very negative, it's like saying MySQL has been took over by Oracle so we must stop using MySQL because in a few years they might drop it. Also it's not silverlight, it's WPF - which ain't going anywhere, it's a major part of the DotNet Framework which is "replacing" Windows Forms. Don't think Capita redeveloped everything going from DotNet2 to 4 do you? No they changed a dropdown then left the rest to the build server to run the unit testing.

  • 2 weeks later...
Posted

Desktop side

Core 2 Duo E4300 = 1.8ghz

Core 2 Duo E6300 = 1.87ghz

 

Laptop side (the low voltage core2duo are far slower)

Core 2 Duo SL7100 = 1.2ghz

Core 2 Duo U7600 = 1.2ghz

in fact it goes as low as 1.07ghz for the Core 2 Duo U7500

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...