-
Notifications
You must be signed in to change notification settings - Fork 3
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
YAML Support for Model Specification #23
Labels
Comments
Closed
I was thinking about this and was wondering if it would be useful to add a JSON format option too? I think Boost property tree has a built in parser. |
Adding JSON support is not needed at this time since users rarely code JSON directly. |
Is this still something worth looking into? I have the work saved on this branch |
Not at this time. Focus on the Python bindings.
…--
Reed A. Cartwright, PhD
Barrett Honors Faculty
Assistant Professor of Genomics, Evolution, and Bioinformatics
School of Life Sciences
Human and Comparative Genomics Laboratory
The Biodesign Institute
Arizona State University
==================
Availability: http://links.asu.edu/CartwrightCalendar
Address: The Biodesign Institute, PO Box 875301, Tempe, AZ 85287-5301 USA
Packages: The Biodesign Institute, 1001 S. McAllister Ave, Tempe, AZ
85287-5301 USA
Office: Biodesign B-220C, 1-480-965-9949
Website: http://cartwrig.ht/
On Wed, Feb 7, 2018 at 5:16 AM, Zach ***@***.***> wrote:
Is this still something worth looking into? I have the work saved on this
branch <https://github.com/zmertens/dawg/tree/feature/yaml>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/reedacartwright/dawg/issues/23#issuecomment-363643216>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGOHpp_v3eLHjJC9npBqNBp9UA_kQOEks5tSRWpgaJpZM4KOa3t>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Dawg 2.0 currently uses a custom parameter file format.
YAML is a popular and flexible markup language and being able to specify models using YAML would leverage a lot of existing tools.
The text was updated successfully, but these errors were encountered: