Use new (spec) input editors to replace legacy editors - #163
Open
walterxie wants to merge 5 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See #157 and fix #162
Replaces the deprecated
ParameterInputEditorwith the specScalarInputEditor/VectorInputEditorpair, and removes the now-unusedLegacyStandard.xmltemplate.ParameterInputEditoras an InputEditor service; registerspec.VectorInputEditor.BeautiDoc.scrubAll()resolvingSiteModelInputEditor.customConnectorto the legacy class instead of
spec.SiteModelInputEditor; updateSubstModels.xml/Standard.xml connectors accordingly.
BranchRateModel.Baseinstead of specBaseRealScalarParaminsteadof
ScalarDistribution, so it never showed for a prior's ownhyperparameters (e.g. Gamma's alpha/theta)
not just the operator's parameter list; added
TensorDistributionInputEditorTest for Dirichlet incorrectly displayed in the Prior panel #160 (Dirichlet vs IID offering).
Follow-up not included here: VectorInputEditor has no hyperprior-reveal
branch, and BeautiConfig's hyperprior template still builds legacy
Prior/OneOnX/ScaleOperator objects instead of spec ones.