sehHeiden
I am searching for version to plot two dataframes with the same colon name into a layer each. I tried it in VegLite Json:
{
"$schema": "https://vega.github.io/schema/vega-lite/v5.json",
"data": {
"values": [
{"x": 1, "y": 10},
{"x": 2, "y": 20},
{"x": 3, "y": 15}
],
"name": "data1"
},
"layer": [
{
"data": {
"values": [
{"x": 2, "y": 30},
{"x": 3, "y": 25},
{"x": 4, "y": 35}
],
"name": "data2"
},
"mark": "line",
"encoding": {
"x": {"field": "x", "type": "quantitative"},
"y": {"field": "y", "type": "quantitative"},
"color": {"value": "blue"}
}
},
{
"data": {"name": "data1"},
"mark": "line",
"transform": [
{"filter": {"field": "x", "range": [2, 3]}}
],
"encoding": {
"x": {"field": "x", "type": "quantitative"},
"y": {"field": "y", "type": "quantitative"},
"color": {"value": "red"}
}
}
],
"resolve": {
"scale": {
"x": "shared",
"y": "independent"
}
}
}
What I came up with in Elixir draws the seconds DataFrame so that, it is WWWWAY to high over the correct place and the y range is evenly wrongly scaled:
def create_compare_graph(data_a, data_b, title, col) do
Vl.new(width: 500, height: 300, title: title)
|> Vl.data_from_values(data_a,
only: ["day", col])
|> Vl.layers([
Vl.new()
|> Vl.mark(:line, color: "blue")
|> Vl.encode_field(:x, "day",
type: :quantitative,
title: "Day of the year"
)
|> Vl.encode_field(:y, col,
type: :quantitative,
scale: [domain: [0, 1]],
title: "DF1"),
Vl.new()
|>Vl.data_from_values(data_b,
only: ["day", col])
|> Vl.mark(:line, color: "red")
|> Vl.encode_field(:x, "day",
type: :quantitative,
title: "Day of the year")
|> Vl.encode_field(:y, party,
type: :quantitative,
scale: [domain: [0, 1]],
title: "DF2")
])
|> Vl.resolve(:scale, y: :independent)
end
end
Example Data:
DF1:
day value
| 250 | 0.125
| 251 | 0.13
| 252 | 0.13
| 256 | 0.14
| 257 | 0.14
DF2:
day value
| 250 | 0.36
| 251 | 0.36
| 252 | 0.36
| 256 | 0.36
| 257 | 0.36
If possible I would prefer to do it, in Tucan as the code locks much cleaner with it. ![]()
Trending in Questions
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
Hello,
I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
So my question is quite simple and i have found no conclusive answer on forum, google or AI.
Should we use :erlang.float for Integer to ...
New
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
Documentation
While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself.
My main conc...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #ai
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming











Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sehHeiden
A reply to myself.
VegaLite-datasets_from_values allows several sources.
I tried to apply it with:
Error:
Edited: the error Because chcnage Vl.Data → Vl.data
awerment
Are the domains in the real data significantly different? If so, does setting the scale resolution to
:sharedhelp? (|> Vl.resolve(:scale, y: :shared)Without a legend, independent scales can look confusing, although the chart is correct:
With
:shared:sehHeiden
Sorry,
I did have a data error. And did not change the varible. Therefore they ware out of scale.
I also applied Tucan. Which greatly reduces the amount of code.
The only thing I would like to add is a Legend.
sehHeiden
Solved it somewhat with Annotate.