Frequency Rankings with stock cooler

Why its allowed to have like specifications that they are running stock cooler.. but have pictures with LN2 cooling.. Because i run like 4.9Ghz on stock cooling have the pics and validation.. but if i filter search on stock cooling and people above me use LN2 but have stock put in the fields..

Are u gonna fix this hwbot..? Its not fair..

But overall u do very good Job.. have to say that too

Thnxx Greetss ClockMasters Netherlands..

Most of those are user errors .

It's nearly impossible to (automatically) identify what cooling was used based on a screenshot or even a system picture.

Is it possible to force the users to double-check this entry, e. g. if the CPU frequency is above 5 GHz or if the achieved frequency is within the first third there appears a reminder in case you selected stock cooling?

Ok thank for the fast answer..!

Yeah automatically would be very difficult..

But is there not an admin that is allowed to check it.. and change it..

For at least the top 20 or 10..

Not that hard i guess.. But yeah who am i to say that ghehe..

But thanxx Greetss ClockMasters

But is there not an admin that is allowed to check it.. and change it..

Hoo Yeaaaahhh, :banana:

Please Massman check every submission submited on hwbot

@ClockMasters:

If you find wrong submissions, please feel free to report them and we (moderators/admins) will take a look and edit/check/block if it's needed.

Is it possible to force the users to double-check this entry, e. g. if the CPU frequency is above 5 GHz or if the achieved frequency is within the first third there appears a reminder in case you selected stock cooling?

In theory, yes. Practically, it's quite complicated, though, as it's not so easy to define the detection barrier in a simple definition. Not all CPUs require LN2 for 5GHz and what about videocards.

We could add a simple pop-up whenever 'stock cooling' is selected, but then we'd be annoying those who do actually submit with stock cooling .

Now stock cooling doesn't make sense anymore,

I mean there is not even stock cooling for the X79 CPU afaik

And for the cpu like FX-8150, it's a watercooling.

So ''stock cooling'' can be crap piece of aluminium, asetek watercoolink, heatpipe cooler....

Maybe we need to change the default field into:

Unknow or not specified and make it mandatory to change

so when submiting we always need to change this field otherwise it will be ''Validation error: cooling not specified''

Especialy that now the rankings/leagues are sorted by cooling used

most people ignore the cooling tab when they submit a score ... a solution would be to make it empty by default, not "stock cooler" as it is now

most people ignore the cooling tab when they submit a score ... a solution would be to make it empty by default, not "stock cooler" as it is now

Seems like the best option. I'll add it to the planning.

//edit: then again ... what about mainboard/memory/videocard?

Do you think it's an alternative to choose an empty field instead of "stock cooling" as default, so you have to choose a proper cooling method to submit your result successfully? Stock cooling is likely not the cooling method used for most results (atleast for CPUs), so most overclockers have to click at the drop down menu anyway if they want to choose the right cooling method (except they're lazy/sloppy and that leads to the problem we're discussing now.)

Edit: Hate it to be too late.

//edit: then again ... what about mainboard/memory/videocard?

Only mandatory CPU + videocard imo, 95% of the time motherboard and memory are aircooled.

Edit: Hate it to be too late.

Mouhahaha

Yep, usually if a value needs to be selected the dropdown options look like this:

<option selected="selected">-- Select cooling --</option>

<option>Stock</option>

<option>Air</option>

<option>Water</option>

<option>SS</option>

<option>Dry Ice</option>

<option>Cascade</option>

<option>LN2</option>

<option>LHe</option>

When nothing selected (default option left) there's a validation error that you must select your cooling.

So I think this is the best solution.

Yep, usually if a value needs to be selected the dropdown options look like this:

 

<option selected="selected">-- Select cooling --</option>

<option>Stock</option>

<option>Air</option>

<option>Water</option>

<option>SS</option>

<option>Dry Ice</option>

<option>Cascade</option>

<option>LN2</option>

<option>LHe</option>

 

When nothing selected (default option left) there's a validation error that you must select your cooling.

 

So I think this is the best solution.

Sounds like an great solution..

Oh, and another thing:

From usability point of view mandatory fields should be easily distinguishable.

The most popular solution is to mark all mandatory fields with a red asterisk after the label, like this:

Note that you have a legend next to submit button - [*: required field], but none of the fields are marked that way. Only the fieldset legend for processor is marked

The way it is done currently and because the fact that not all fields have labels, it might be easier to add an explanation to the legend of every fieldset, as it's done for [verification (mandatory)].

For CPU you could have something like this in the legend text for the fieldset "processor (processor and cooling required)".

The point is that the user should have a visual information about required info he needs to enter on the initial stage, not only after Submit button clicked.

Aside from that, one thing that had been noted before. Please change the tooltip position, so it appears on top of the field, not on right and covering the next field that is supposed to be filled. IMO it would be better.

$(function(){
    $("input[title]").tipTip({maxWidth: "auto", activation: "focus", defaultPosition: "[b]top[/b]", delay: "100"});
});

Oh, and another thing:

From usability point of view mandatory fields should be easily distinguishable.

The most popular solution is to mark all mandatory fields with a red asterisk after the label, like this:

 

Note that you have a legend next to submit button - [*: required field], but none of the fields are marked that way. Only the fieldset legend for processor is marked

The way it is done currently and because the fact that not all fields have labels, it might be easier to add an explanation to the legend of every fieldset, as it's done for [verification (mandatory)].

For CPU you could have something like this in the legend text for the fieldset "processor (processor and cooling required)".

 

The point is that the user should have a visual information about required info he needs to enter on the initial stage, not only after Submit button clicked.

 

Aside from that, one thing that had been noted before. Please change the tooltip position, so it appears on top of the field, not on right and covering the next field that is supposed to be filled. IMO it would be better.

 

$(function(){
    $("input[title]").tipTip({maxWidth: "auto", activation: "focus", defaultPosition: "[b]top[/b]", delay: "100"});
});

I agree with this suggestion. it would make it easier.

Vin

Oh, and another thing:

From usability point of view mandatory fields should be easily distinguishable.

The most popular solution is to mark all mandatory fields with a red asterisk after the label, like this:

 

Note that you have a legend next to submit button - [*: required field], but none of the fields are marked that way. Only the fieldset legend for processor is marked

The way it is done currently and because the fact that not all fields have labels, it might be easier to add an explanation to the legend of every fieldset, as it's done for [verification (mandatory)].

For CPU you could have something like this in the legend text for the fieldset "processor (processor and cooling required)".

 

The point is that the user should have a visual information about required info he needs to enter on the initial stage, not only after Submit button clicked.

 

Aside from that, one thing that had been noted before. Please change the tooltip position, so it appears on top of the field, not on right and covering the next field that is supposed to be filled. IMO it would be better.

 

$(function(){
    $("input[title]").tipTip({maxWidth: "auto", activation: "focus", defaultPosition: "[b]top[/b]", delay: "100"});
});

good idea