EMULAB Forum
clrmamepro [English] => clrmame Discussion => Topic started by: yescabernetnointernet on 20 May 2020, 20:09
-
Hi to all cmamep guys!! 8)
As in topic's title: I'd like to learn how to properly filter my sets in Scanner before going on with useless rebuilding.
What is the syntax to use? Where can I set desired filters? :o
I'd like to filter my sets using node from DATs to exclude all "driver status="preliminary"". I know, I'm aware of the "risks" of filtering sets with this, I am ok with that.
Also, please tell me if it's good to unset [MECHANICAL] from Scanner--->Systems, or should I take extra steps?
And also: could cmamep take advantage of catver.ini (http://www.progettosnaps.net/catver/) (from AntoPISA' progettoSNAPS) to help users filter their sets?
Many many thanks!!
Bye 8)
-
Scanner->Scan Results Tree Window -> Set Information -> Select Sets: %D=preliminary, hit apply, hit invert, check 'initial invert'.
If you hover over the drop down box in select sets, you get an idea of possible variables.
If it's good to unset Mechanical, no...Same for any other restrictions. I'd prefer to keep everything enabled.
catver.ini, no but in setinformation you can load a file with setnames to filter (From File)
-
Hey Roman! (https://www.emulab.it/forum/index.php?action=profile;u=62)
catver.ini, no but in setinformation you can load a file with setnames to filter (From File)
Let's see if I understood correctly... When you say setnames and (From File), you mean a *.txt file with inside what? ... ;D I mean, I don't need filtering particular stes by their names, I need to filter them by DAT' nodes... I'm a little confused... ;D :-[
-
The "select sets" box allows all kind of filtering (by name, by description, being a parent, etc etc...etc..).
"from file" is a simple text file which holds one setname per line. Each listed one will be enabled, not listed ones disabled (unless you use things like "initial invert")
-
Scanner->Scan Results Tree Window -> Set Information -> Select Sets: %D=preliminary, hit apply, hit invert, check 'initial invert'.
I've get same results without "Invert", but using "Logical NOT". Can you confirm?
Also: deselecting "%D=preliminary" it disables also all [MECHANICAL]. Can you confirm?
-
well, yes, as long as you only have one selection, a logical not is the same as the invert. Regarding MECHANICAL deselection, well if each mechanical set is marked as driver status="preliminary" in MAME's output then yes....otherwise no....I didn't check....take a look at MAME's -listxml output
-
(https://i.ibb.co/TKXTt86/Set-Information-mame221-dat-17599-41857-Sets-73-73-BIOS-56-56-CHD-Regions.jpg) (https://ibb.co/TKXTt86)
What about "Incl." checkboxes? Why aren't them checked by default? ... :o
-
because nobody should disable sets ;-) There is really no need.
-
Ahem... But... "Incl." does't means include? It's somewhat misleading for me :P ;D ;D ;D So, if I check "Incl." I'm telling cmamep to exclude sets? Do I understand correctly? :)
-
Actually in setinformation you get information about sets (erm...yeah). It shows you the single files within sets and you can check/uncheck sets. So you can include or exclude sets. This can be done by
- click the checkbox before the set
- use the select sets box
- use the "from file" box
- use the avail sets, select all, select none, invert buttons
"incl. clones, incl. parent, etc" checkboxes simply affect your selection by automatically enabling the parent, all clones etc. So if you e.g. select a clone and have "incl. parent" enabled, it also enables the parent.
"logical not" inverts the selection but on each single subselection (you can have multiple selections in select sets like A;B it becomes not(A) and not(B))
if "initial invert" is ticked your selection gets inverted each time the profile is loaded (so you don't need to use the invert button each time)
So...it's not all about excluding or including, it's both.
-
"incl. clones, incl. parent, etc" checkboxes simply affect your selection by automatically enabling the parent, all clones etc. So if you e.g. select a clone and have "incl. parent" enabled, it also enables the parent.
Glad to learn that. :)
"logical not" inverts the selection but on each single subselection (you can have multiple selections in select sets like A;B it becomes not(A) and not(B))
Good: now it's clear for me that "Logical NOT" applies to all the options. As you said: "on each single subselection" now I understood.
if "initial invert" is ticked your selection gets inverted each time the profile is loaded (so you don't need to use the invert button each time)
That was the trickiest concept: "your selection gets inverted" and "you don't need to use the invert button each time". Now it's crystal clear!!! ;) 8)
Thank you Roman (https://www.emulab.it/forum/index.php?action=profile;u=62), you're so kind and patient!!! ;)
-
you're welcome...and that's what this forum is made for.....asking questions
-
Done some tests. Roman (https://www.emulab.it/forum/index.php?action=profile;u=62), please have a look at them.
>> 1st run (New Scan)- %D=preliminary
- logical NOT = checked
- Incl. * = all unchecked
- click Apply
1st run results:Missing
·Sets 2253/13048
·ROMs 13689/160677
·CHDs 40/268
·Samples 137/2176
·Bytes 4gb/78gb
Fixed Wrong Case
·Sets 0/0
·ROMs 0/0
·CHDs 0/0
·Samples 0/0
Fixed Unneeded
·Sets 0/0
·ROMs 0/0
·CHDs 0/0
·Samples 0/0
Fixed Wrong Name
·Sets 0/0
·ROMs 0/0
·CHDs 0/0
Fixed Wrong Size
·ROMs 0/0
Fixed Wrong Date Time
·ROMs 0/0
Wrong Hashes
·Wrong CRC32 ROMs 0
·Wrong SHA1 ROMs 0
·Wrong MD5 ROMs 0
·Wrong SHA1 CHDs 0
·Wrong MD5 CHDs 0
Corrupt Containers 0
---------------------------------------
Active Sets 13048/35263
·Parents 2136/5038
·Clones 6473/22688
·Others 4366/7464
·BIOS 73/73
Active ROMs 160677/295264
·Parents 32749/52204
·Clones 98014/174545
·Others 26676/62082
·bad dumps 940/2111
·no dumps 1793/3817
·verified dumps 0/0
·BIOS 505/505
Active CHDs 268/1070
·Parents 50/151
·Clones 91/249
·Others 74/369
·bad dumps 50/144
·no dumps 2/156
·verified dumps 0/0
·BIOS 1/1
Active Samples 2176/18454
·Parents 385/392
·Clones 1570/17826
Active Bytes 78gb/257gb
In this 2nd run I was expecting fewer sets, but it's the exact opposite!! :o
>> 2nd run (Scan)- %D=preliminary
- logical NOT = checked
- Incl. * = all checked
- click Apply
2nd run results:Missing
·Sets 2675/13470
·ROMs 17148/166701
·CHDs 47/284
·Samples 235/2274
·Bytes 5gb/80gb
Fixed Wrong Case
·Sets 0/0
·ROMs 0/0
·CHDs 0/0
·Samples 0/0
Fixed Unneeded
·Sets 0/0
·ROMs 0/0
·CHDs 0/0
·Samples 0/0
Fixed Wrong Name
·Sets 0/0
·ROMs 0/0
·CHDs 0/0
Fixed Wrong Size
·ROMs 0/0
Fixed Wrong Date Time
·ROMs 0/0
Wrong Hashes
·Wrong CRC32 ROMs 0
·Wrong SHA1 ROMs 0
·Wrong MD5 ROMs 0
·Wrong SHA1 CHDs 0
·Wrong MD5 CHDs 0
Corrupt Containers 0
---------------------------------------
Active Sets 13470/35263
·Parents 2174/5038
·Clones 6857/22688
·Others 4366/7464
·BIOS 73/73
Active ROMs 166701/295264
·Parents 33132/52204
·Clones 103233/174545
·Others 26676/62082
·bad dumps 1139/2111
·no dumps 2016/3817
·verified dumps 0/0
·BIOS 505/505
Active CHDs 284/1070
·Parents 51/151
·Clones 100/249
·Others 74/369
·bad dumps 54/144
·no dumps 4/156
·verified dumps 0/0
·BIOS 1/1
Active Samples 2274/18454
·Parents 385/392
·Clones 1668/17826
Active Bytes 80gb/257gb
-
The only important information is the scan results tree window. Forget about stats. Look at the listed items in the tree output.
It's pretty normal with your settings that the 2nd run shows more missing etc. With your changed selection, you've included way more sets.
-
With your changed selection, you've included way more sets.
So...
"logical NOT" checkbox only affects the above "Select Sets" string.
And Logical NOT does not affect the "Incl." checkboxes.
-
The incl.* fields are used to mark parents/clones/devices/bios/etc from the selected sets.
So if you select sets selects 3 sets, a mark parents then marks the parent sets of the chosen 3 (which might already be parent sets though)...
But anyway...your 2nd scan includes more sets....so you can of course have more issues reported ;-)
-
"logical not" inverts the selection but on each single subselection (you can have multiple selections in select sets like A;B it becomes not(A) and not(B))
So...it's not all about excluding or including, it's both.
The incl.* fields are used to mark parents/clones/devices/bios/etc from the selected sets.
So if you select sets selects 3 sets, a mark parents then marks the parent sets of the chosen 3 (which might already be parent sets though)...
But anyway...your 2nd scan includes more sets....so you can of course have more issues reported ;-)
I think I misunderstood you words... ;D
So the "logical NOT" checkbox affects only "Select Sets" field. Am I right now? ???
-
It is applied on any part of select sets. The checkboxes are applied after that.
Examples:
s* selects all sets where the setname starts with s
s* + tick incl. parent and incl. clones will select all starting with s PLUS their parents and clones (which not necessarily have to start with s)
s* + logical not will select all sets not starting with s
s* + logical not + incl. parent and incl. clones not will select all sets not starting with s PLUS their parents and clones (which may start with s)
s*;t* will select sets starting with s or t
s*;t* + logical not is actually a not (s*) OR not (t*) which is actually everything(!!!) so beware of a logical not on a multiselect
-
OK! Thanks.