Renaming ce to contrast precludes the use of contrast in statistical derivatives
See original GitHub issue#464 breaks FitLins. I recognize that these derivatives aren’t standardized, but neither is “contrast” a standardized name for the “ce” entity. As it is, trying to parse a FitLins derivatives structure yields:
*** sqlalchemy.orm.exc.FlushError: New instance <Entity at 0x2b8e1e860c18> with identity key (<class 'bids.layout.models.Entity'>, ('contrast',), None) conflicts with persistent instance <Entity at 0x2b8e1d8da208>
Issue Analytics
- State:
- Created 4 years ago
- Comments:24
Top Results From Across the Web
Orthogonal contrasts - University of Southampton
Orthogonal contrasts for analysis of variance are independent linear comparisons between the groups of a factor with at least three fixed levels.
Read more >Contrast (statistics) - Wikipedia
In statistics, particularly in analysis of variance and linear regression, a contrast is a linear combination of variables (parameters or statistics) whose ...
Read more >7.2 - Contrasts | STAT 555
For other comparisons we will use contrasts. What is a contrast? A contrast is essentially a difference in regression coefficients.
Read more >Monetary and Financial Statistics Manual and Compilation ...
Scope and Uses of Monetary and Financial Statistics ... In contrast, equity on the liability side of the ... naming conventions.
Read more >SPM12 Manual - Wellcome Centre for Human Neuroimaging
32.2.5 F-contrasts for testing effects of movement . ... To check the order of slices within an image file, use the SPM Display...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yeah, fine with me. It’s an uncommon enough entity, and a quick enough follow-up change, that I doubt many people (possibly no one) will notice we broke it twice.
I’m okay with this.
@tyarkoni This only changes agent -> ceagent at this point. Does that seem small enough to not go through a major refactor?