You do need to better understand the data model, and that is made much clearer if you can adopt the native .dx file format instead of .general.
General format is just for simple data sets. DX format covers all that general can do and far more. By structuring the data in .dx format
prior to import, you can save a lot of work inside DX. That said, the Structuring modules permit one to do many complex operations
that would otherwise require external coding.
The idea of Mark is to temporarily make any component of a field containing many components, the 'data' which is the keyword
component that most modules operate on. Unmark then puts the 'data' back into the named component (or the previously Marked
component by default). If you have separate fields each with its own data component, they are as you see quite distinct. You want
to achieve the state where you have one field with more than one 'data-like' component, but of course with unique names to
keep the data components distinct. Then, to operate on a particular one, say to color by, Mark that one. To Glyph by another,
Unmark the first, and Mark the second, and so on.
As I say, let's return this thread to the list where you will get more help and opinions.
On Monday, Jun 2, 2003, at 04:07 America/New_York, Klaas Gadeyne wrote:
_______________________________3. Use Print("rd") (module) to see what comes out of any module that
you're not sure of, esp. in this case, Import. That's the diagnostic
tool (like printf) to monitor the data flowing in the net. Off-hand,
your .general file seems OK, so I don't have any suggestions.
Hi Chris,
Apparently (this seems to be confirmed by the documentation of the "mark"
module), the input to the mark module _must_ be a field.
So, if I put a "select" ("2") module between the import module and the
mark module for selecting the second field, I can select "field2", mark
the data as "data", filter it through the "include" module, and the unmark
the data.
This works fine. Field2 is then filtered as I want to. However, this
operation does not succeed on filtering the "positions" of field0 and
field1.
It seems thus that the mark module is not what I want and I'll have to
look for another module (or write one myself :-( )
Another option would be to have just one field (field0), and then select
the subparts in another way?
Anyway, Thx a lot for your help!
Klaas
Chris Pelkie
Scientific Visualization Producer
622 Rhodes Hall, Cornell Theory Center
Ithaca, NY 14853
