Search  
  

Please login to post into the forums. Remember - keep your posts friendly. 

Note: CBIT reserves the right to remove any material it considers inappropriate or offensive. Please report any undesirable posts or behaviour to support@lucidcentral.org.

If you have any direct support requests such as reactivation requests please use the help desk.

  
  

Login

    
  
HomeHomeLucid3 Discussi...Lucid3 Discussi...Building and us...Building and us...multistate character issuemultistate character issue
Previous
 
Next
New Post
1/16/2012 8:18 AM
 

Hi Matt et al.

I am continuing to refine ID keys to the echolocation calls of bats.  I want to add a new grouping variable under features but can not seem to get it to become a multistate feature and only  Grouping or Numeric variables was offered.

As I was unable to create a new set of characters as  noted above I copied another Multistate feature set I have in the key and renamed items and deleted the unnecessary ones.

 So my main question is what would the best way be to set up a conditional set of values for measurements?

 I have a set of numeric values that works very well for various call parameters that separate the species.

Simply adding the  "background" features of  where the calls were recorded will not work.

This may influence the measures when the bats are recorded.

 E.G. if the calls are recorded in open area w/o background clutter the call parameters I have scored work 100%.

IF the bats are leaving a roost or flying in heavy clutter (forest understory) many of the call parameter values will shift in values.

 I can create a simple multistate character  "background" with the simple +/- check boxes in the scoring, but that will not reflect the different call parameter values that would be associated with the background state.

How can I add this to the key and have it  linked to the additional call parameters, short of creating several different features classes for each background type... Open, clutter etc.???

 
New Post
4/26/2012 2:12 PM
 

Hi Bruce,

For your first part I think what you are trying to achieve is a mix of groups and states at the same level this is disallowed in the Builder, which is why you only get those two options.

For the second part of your post I think one way to achieve this is to create separate 'conditional set of values for measurements' (numeric characters) for each of the different background features. You can then use Positive Dependencies to bring in the best 'conditional set of values for measurement' numeric character based on what background feature was selected.

I hope I've understood what you are trying to achieve.

Cheers,

Matt.

 
Previous
 
Next
HomeHomeLucid3 Discussi...Lucid3 Discussi...Building and us...Building and us...multistate character issuemultistate character issue


  
Copyright 2013. All rights reserved.
Terms Of Use  Privacy Statement