Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some user suggestions for tagging #1

Open
jiversen opened this issue Aug 16, 2019 · 1 comment
Open

Some user suggestions for tagging #1

jiversen opened this issue Aug 16, 2019 · 1 comment

Comments

@jiversen
Copy link

Hello, trying tagging for the first time and overall impressed with this tool! The searching and ability to add new tags is great

The following are suggestions for things I'd like to be able to do:

  1. some of my events' fields already contain HED-like information. I would like to be able to create tags like 'Prefix/<>' that would (optionally) add a prefix to the HED tag-like information already in the fields.

  2. The ability to handle numeric fields--right now the tagger crashes matlab if a numeric field was chosen, perhaps because the tagger is creating a unique category for each value (?). Instead, if I have a field called 'angle', I'd want to create tags like 'Attribute/angle/<<#>>' where the <<#>> is filled in from the field value. It's related to 1)

  3. I have boolean fields with some values as NaN. The tagger only shows 0 & 1. It should also show NaN, in case I wanted to give that a specific meaning

Maybe these are already possible, but it was not clear to me how to accomplish it. Is there any documentation on the process?

@VisLab
Copy link
Member

VisLab commented Aug 18, 2019

On item 3:

Attribute/Angle/30 degrees

or

Attribute/Angle/0.5 radians

should validate. What version of the validator are you using? Also, can you please try to validate your actual tags at:

http://visual.cs.utsa.edu/hed

We are in the process of switching the Matlab code to validate using an underlying python validator and that is the one that we are correcting.

The NaN issue is interesting. Right now you need to remove the value entirely to represent NaN. We may need to add another option like "Unknown" for any value. NaN is probably not what we want, since some values can be strings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants