Holomark2_R6

I’m pretty sure you’re kidding.
What I mean is similar to what Steve suggests. Other alternatives would be a comma separated text file with a line for each data item in a label, data value format with the same number of lines in each file even if some of the lines have no data.
Or perhaps you are sufficiently sophisticated (I know you are) to output an xml file with a label-data format.

Eventually, when that database author completes his/her job, each user could submit the data without involving you. Not a bad idea?

I would just write a dictionary. The next person to pick this up can choose to convert the dictionary into CSV, XML, JSON, …

I’m thinking, Steve, that McNeel servers would be the place for such a database because then the submitter could be authenticated and perhaps even an exchange could take place between Holomark and the database to validate and quality control the submission. Just spitballin’ here.

1 Like

Holomark 2 R6 v2,60

Total Score: 36431
Total Runtime: 229.48 sec

GPU scores: 29640
GPU_01 - 84.40 fps - Cube 4 tests
GPU_02 - 36.10 fps - UDT Shape
GPU_03 - 83.30 fps - Wireframe
GPU_04 - 72.50 fps - Shaded
GPU_05 - 64.10 fps - Rendered
GPU_06 - 73.50 fps - Block Rendered
GPU_07 - 24 units Nurbs @ 5 fps in Wireframe
GPU_08 - 21 units Nurbs @ 5 fps in Shaded
GPU_09 - 73 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 85.50 fps - RenderMesh Render
GPU_11 - 200.00 fps - RenderMesh RenderSpeed
GPU_12 - 172.40 fps - JoinedMesh Render
GPU_13 - 322.60 fps - JoinedMesh RenderSpeed
GPU_14 - 20 units mesh @ 15 fps in Shaded
GPU_15 - 59 units mesh @ 15 fps in Render
GPU_16 - 123 units mesh @ 15 fps in RenderSpeed
GPU_17 - 66.70 fps - mesh in Rendered Studio
GPU_18 - 26.20 fps - Nurbs in Rendered Studio
GPU_19 - 35.30 fps - Block Illustration
GPU_20 - 41.30 fps - 2D single
GPU_21 - 16.20 fps - 2D massive (20x)

CPU scores: 6791
CPU_01 - 10.63 sec - Booleans and Contours
CPU_02 - 3.04 sec - Twist and Taper (UDT)
CPU_03 - 13.66 sec - Meshing Mini
CPU_04 - 0.09 sec - Extract Render Mesh
CPU_05 - 0.06 sec - Join Render Mesh
CPU_06 - 36.33 sec - Reduce Mesh
CPU_07 - 2.97 sec - Calculating Technical display
CPU_08 - 6.84 sec - Making Silhouettes

ASUSTeK COMPUTER INC.
G771JM

NVIDIA GeForce GTX 860M - 2048.0 MB
DriverVersion: 25.21.14.1634
Intel® HD Graphics 4600 - 1024.0 MB
DriverVersion: 20.19.15.4549

Intel® Core™ i7-4710HQ CPU @ 2.50GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 2.5 GHz

TotalPhysicalMemory: 12.0 GB

Microsoft Windows 10 Home

  • None - 64-bit

Rhino 6 sr 12 64 bit
AA level = 4

No I wasn’t, I live on a need to know basis regarding programming :wink:
But I did make semicolon separated data (I think it was semicolon I used) for Holomark1. Then I collected that in excel where I could quickly sort by scores for each test. So if you give me an example xml file then I can most certainly output to that. (After googeling a bit…)

Holomark 2 R6 v2,60

Total Score: 58099
Total Runtime: 234.87 sec

GPU scores: 42120
GPU_01 - 170.20 fps - Cube 4 tests
GPU_02 - 50.00 fps - UDT Shape
GPU_03 - 322.60 fps - Wireframe
GPU_04 - 156.30 fps - Shaded
GPU_05 - 67.60 fps - Rendered
GPU_06 - 50.80 fps - Block Rendered
GPU_07 - 162 units Nurbs @ 5 fps in Wireframe
GPU_08 - 47 units Nurbs @ 5 fps in Shaded
GPU_09 - 27 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 76.90 fps - RenderMesh Render
GPU_11 - 156.30 fps - RenderMesh RenderSpeed
GPU_12 - 106.40 fps - JoinedMesh Render
GPU_13 - 277.80 fps - JoinedMesh RenderSpeed
GPU_14 - 9 units mesh @ 15 fps in Shaded
GPU_15 - 30 units mesh @ 15 fps in Render
GPU_16 - 41 units mesh @ 15 fps in RenderSpeed
GPU_17 - 41.80 fps - mesh in Rendered Studio
GPU_18 - 14.40 fps - Nurbs in Rendered Studio
GPU_19 - 18.30 fps - Block Illustration
GPU_20 - 125.00 fps - 2D single
GPU_21 - 57.80 fps - 2D massive (20x)

CPU scores: 15979
CPU_01 - 8.56 sec - Booleans and Contours
CPU_02 - 1.95 sec - Twist and Taper (UDT)
CPU_03 - 3.62 sec - Meshing Mini
CPU_04 - 0.03 sec - Extract Render Mesh
CPU_05 - 0.35 sec - Join Render Mesh
CPU_06 - 12.01 sec - Reduce Mesh
CPU_07 - 0.98 sec - Calculating Technical display
CPU_08 - 3.79 sec - Making Silhouettes

Hewlett-Packard
h9-1185

AMD Radeon HD 7700 Series - 2048.0 MB
DriverVersion: 24.20.13019.1008

Intel® Core™ i7-3770 CPU @ 3.40GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 3.4 GHz

TotalPhysicalMemory: 16.0 GB

Microsoft Windows 10 Home

  • None - 64-bit

Rhino 6 sr 11 64 bit
AA level = 4

hi Jørgen,

thanks for the update :slight_smile:

I have 2 suggestions for a small improvement if you plan to spend even more time on this:

  1. why not set a default AA options for everyone so the scores are easier to compare? (say: 4)
  2. it would be cleaner if the plugin deleted all custom display modes on exit so they don’t clutter the UI

–jarek

Hi Jarek,
That’s two for two! I agree on both, but don’t know how to do either of them :wink:
I have to install the display modes to control the environment, and that is through a hack… and I don’t know how to uninstall them with a script. It wasn’t possible when Holomark2 was released though, sorry about that.
Regarding AA then all I know is how to read the value, not how to set it. I didn’t think it was possible, but I might be wrong there!

The code I use is this:

import Rhino

AA = "None"
AAlevel=Rhino.ApplicationSettings.OpenGLSettings.AntialiasLevel
if str(AAlevel) == "Draft" : AA = 2
elif str(AAlevel) == "Good" : AA = 4
elif str(AAlevel) == "High" : AA = 8

print AAlevel

(I use the AA value to show in the score, since “draft”, “good” etc isn’t what the user chooses from.

Hi Jorgen -

https://developer.rhino3d.com/api/RhinoCommon/html/M_Rhino_Display_DisplayModeDescription_DeleteDiplayMode.htm

-Pascal

Thanks man, but I don’t understand how to read those pages…
… oh a bit wiser every day…

1 Like

This one says you can get or set AA:
https://developer.rhino3d.com/api/RhinoCommon/html/P_Rhino_ApplicationSettings_OpenGLSettings_AntialiasLevel.htm

Hi Jorgen - how are you adding the modes?

-Pascal

That’s a trade secret…
(that’s a joke though, but it is so hacky so I can’t recommend it)

But deleting them was quite easy, I’ll add it as an option to Holomark2_R6.

import Rhino
import rhinoscriptsyntax as rs

def deleteDisplaymode(modeName):

    dispMode_ID = rs.ViewDisplayModeId(modeName)
    if dispMode_ID:
        Rhino.Display.DisplayModeDescription.DeleteDiplayMode(dispMode_ID)

deleteDisplaymode("HM2_V6_Wire")
deleteDisplaymode("HM2_V6_Shaded")
deleteDisplaymode("HM2_V6_Render")
deleteDisplaymode("HM2_V6_Illustration")
deleteDisplaymode("HM2_V6_RenderSpeed")

Yes, but if I want to set the value “Good” then I can’t use a string… so how do you think I should do it properly?

Maybe I am missing something, but here are the numbers for different levels:
https://developer.rhino3d.com/api/RhinoCommon/html/P_Rhino_ApplicationSettings_OpenGLSettings_AntialiasLevel.htm

And this seems to work (but I know, I have very hard time figuring out how to use RhinoCommon docs as well!):

    import Rhino
    aa = Rhino.AntialiasLevel.High
    Rhino.ApplicationSettings.OpenGLSettings.AntialiasLevel = aa

–jarek

Smoooth! That works perfectly!
Yes they are “None” “Draft” “Good” High" (or 0, 2x, 4x, 8x as OpenGL calls them)
I do want users to choose what mode to test though as some users will probably benefit from running in “None” mode. I’ll add this to HM3 for sure!

1 Like

IMO, the only AA level for holomark to run at is the level that most users use daily. that is 8x, i assume. why would anyone set it lower? (maybe only if you run rhino on a crappy old laptop)
But I might be wrong about this, since most seem to use 4x for the test run.

I updated to SR11 and updated to the new, yesterday released AMD Adrenalin-Driver 18.12.2 WHQL. Now Holomaork crashes every time when it gets to the end and where it draws the results :frowning:

EDIT:
now it crashed earlier. when it drew the technical view of the minis with dimensions.
I guess it has something to do with the new AMD driver.

If you get any crashdumps or RhinoDotNetCrash.txt on your Desktop be sure to share them with us!