We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
import subprocess | |
get_line_by_line_texlive_dependencies = subprocess.run( | |
[ | |
"apt-cache", | |
"depends", | |
"texlive-full" | |
], | |
universal_newlines=True, | |
stdout=subprocess.PIPE |
# The difference between the `sep` and `collapse` arguments | |
# in paste can be thought of like this: | |
# | |
# paste can accept multiple *vectors* as input, and will | |
# concatenate the ith entries of each vector pairwise | |
# (or tuplewise), if it can. | |
# | |
# When you pass paste multiple vectors, sep defines what | |
# separates the entries in those tuple-wise concatenations. | |
# |
--- | |
title: "GT Quarto Split Table Bug Test" | |
format: | |
docx: default # renders fine | |
html: default # fails with error (see below) | |
pdf: default # fails with error (see below) | |
--- | |
## Test Code |
--- | |
title: Danielak - Statement of Research Experience | |
output: rmarkdown::tufte_handout | |
--- | |
## My experience, knowledge, and interest in PER | |
I spent five years at the University of Maryland--College Park (UMD) as a National Science Foundation Disciplinary Expert in Science Education Research. While there, I was an active member of UMD's Physics Education Research Group (PERG), presenting at the AAPT 2010 Winter Meeting and attending the 2012 AAPT Summer Meeting and PERC. My core areas of expertise, evidenced in both my dissertation[^1] and my first-authored journal publication[^2], include: | |
- **6** years of experience conducting clinical interviews with students and engineers to understand their cognition and practices |
I’m currently working through the book Programming Elm by Jeremy Fairbank. I’m on Chapter 4, where he introduces JSON decoders and the Json.Decode.Pipeline
package. Please bear with me, as I’m an Elm beginner. I’m also working in the Elm repl, as I’m not currently sure how to translate my work into a full Elm program.
In Elm, the order of required
s in a JSON decode pipeline shouldn’t matter for successful decoding, because we’re matching the names of the keys in the JSON oject to the names of the fields in a record. There is no inherent order to the fields of an Elm record, just as there is no inherent order to the properties of a JSON object.
import pandas as pd | |
from siuba import * | |
my_data = { | |
'name': ["Abigail Adams"], | |
'birth': ["1744-11-22"], | |
'death': ["1818-10-28"] | |
} | |
df = pd.DataFrame(my_data) |