Kristoffer Carlsson
Kristoffer Carlsson
The structure above is quite similar how the threaded JuAFEM assembly is done: https://github.com/KristofferC/JuAFEM_Performance_Study/blob/1b67548b8deab2562db141ccddac7ec070548a03/eifel_threaded_juafem.jl#L151-L159 ```jl fill!(K, 0.0) fill!(f, 0.0) for color in colors # Each color is safe to assemble...
I think maybe a `Pkg.instatiate` is needed after activating the new project in `page`.
Oh, I guess I missed it in the docs because I got the error when I executed `serve` which is shown before the section about showing code.
Alternatively, it is already possible to do this from PGFPlotsX: So maybe we should just add some docs on how to do this.
I think the request is to upon saving to `.tex` transform e.g. ``` table[row sep={\\}, x={Dof}, y={Err}] { Dof Err \\ 1.0 2.0 \\ 2.0 1.0 \\ 4.0 0.1 \\...
Seems reasonable but it would be good to check how it impact load times.
It is possible https://github.com/KristofferC/PGFPlotsX.jl/blob/7b41de7160f3a1516e3cefb7eee419a9a55845d1/src/options.jl#L229 should be changed to also call `print_tex` on the `v`s. I just tried something like ```jl @eval PGFPlotsX begin print_opt(io::IO, v::AbstractVector) = print(io, join((print_tex(String, x) for...
Hm, I am not sure this should be done unconditionally. For example, when you export to a .tex file you probably want to use a relative path if that is...
Nice, I thought about this very thing a few days ago after making some hand adjustments to a tex file produced by PGFPlotsX