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

User-unfriendly configuration for butterfly plot #127

Closed
vladdez opened this issue Dec 4, 2023 · 2 comments
Closed

User-unfriendly configuration for butterfly plot #127

vladdez opened this issue Dec 4, 2023 · 2 comments

Comments

@vladdez
Copy link
Collaborator

vladdez commented Dec 4, 2023

image

the field mapping is really hard to understand

  1. what the difference between sensors, label and labels?
  2. what the difference between pos, position, positions?
  3. how to specify them, actually? I do not understand the syntaxis...
  4. we have no documentation or example on them, but they should be
  5. can i safely change argument names to the same underscore format? or are they used somewhere in this form?
  6. how should I specify x and y labels?
  7. is this hierarchy is really necessary? it is really cumbersome, I would rather get rid of it
@behinger
Copy link
Member

behinger commented Dec 4, 2023

1/2 If you have a tuple for e.g. color it just means that the config will check first for a :channel column in your dataframe, next for a :chanels , ext for :trial and then trials - if it cannot fid any of these columns it will show an error, because why are you using butterfly if you don't use that in the first place ;-)
3. plot_butterfly(...,mapping=(;color=:mycolorcolumn)) - I don't think this hierarchy is unecessary
I think it is just a missunderstanding of what we are trying to achieve here
4. There is documentation, we write Multiple defaults will be cycled until match. - but we could be more specific I totally agree. Do you have a better way to write it? Feel free to edit https://github.com/unfoldtoolbox/UnfoldMakie.jl/blob/40111127c2dbdafb7a798dd05f833486dfbe4204/src/docstringtemplate.jl#L41C1-L41C54
5. mh, I think you could just add more. I think these were just some I had used in the past, we can modify them easily imho
6. x/y labels are a property of axis, they are not specifically defined here but are inherited from PlotConfig(:erp) - a user would look into that code anyway. The help should show it
7. you would easily overwrite this using 3

@vladdez
Copy link
Collaborator Author

vladdez commented Dec 4, 2023

cool, I already implemented axis labels with this information
Thanks!

@vladdez vladdez closed this as completed Jul 25, 2024
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