To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.db.invOpen lugnet.db.inv in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Database / Set Inventories / 787
786  |  788
Subject: 
Dichotomous Key
Newsgroups: 
lugnet.cad.mlcad, lugnet.db.inv
Date: 
Thu, 28 Jun 2001 21:38:55 GMT
Viewed: 
65 times
  
One of the grouping features I'd thought of for BrickDraw3D is to group by
stud count. (I haven't made up any palette trees yet, it's just one big
palette so far.)

This is part of a plan to implement a dichotomous key of Lego parts.
A dichotomous key gives a dialog of branching paths designed to narrow your
selection to one. A branch doesn't absolutely have to divide into exactly
two paths. Example of dichotomous keys are a field guide to identifying
plants, or fishes. It's a useful tool, maybe not needed by an expert, but
great for handling the unfamiliar.

I have a number of parts questions in mind. Most of them you will see are
geared to finding a part when you aren't sure what to call it.

How many studs does it have?
Is it mostly rectangular (no curves or diagonals)?
Is it bigger than/smaller than/close to the same size as X
(this is vague. "Taller than" would also be vague because the expected
orientation of a part might be other than the user has in mind.)
Does it have studs on top?

These questions have to be machine-answerable given a part file. Otherwise
they're less useful.

A series of questions that narrows the choice to a few parts could lead to
"is your part one of these?". Supposing that every part has a unique
position in the answer tree, we know the size of every such terminal group
and therefore whether enough questions have been created.  If the user is
baffled and says "no" to the whole group, possibly the tree can be
backtracked, or alternate branches for vague questions can be tried.

Another consideration is to rate how important a part is judging by its
appearance in known set inventories (DAT files). Make sure that that part
can be identified with less questions than some rarely used part (LDRAW has
a lot of old, rare parts.) Do ensure that obscure parts can be found
eventually, however, you don't often need a key for really common parts.

Suggestions welcome.



Message is in Reply To:
  Re: How to customise parts tree in MLCad V2.00R2
 
Jake McKee wrote: [snip] (...) parts (...) Even (...) do (...) playing (...) Probably the only thing that would come close to what you want now would be the favorites category... And similar to what "Ducky Dave" suggested, though less risky, you can (...) (23 years ago, 27-Jun-01, to lugnet.cad.mlcad)

7 Messages in This Thread:


Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR