── Conflicts ────────────────────────────────────────── tidyverse_conflicts() ──
✖ dplyr::filter() masks stats::filter()
✖ dplyr::lag() masks stats::lag()
ℹ Use the conflicted package (<http://conflicted.r-lib.org/>) to force all conflicts to become errors
# label axis and finalize graphhighchart() |>hc_add_series(data = stars,type ="line",hcaes(x = star,y = temp, group = type)) |>hc_title(text ="Star Type and Temperature") |>hc_colors(cols) |>hc_xAxis(title =list(text="Star")) |>hc_yAxis(title =list(text="Temperature (K)")) |>hc_legend(title =list(text="Star Type")) |>hc_legend(align ="right", verticalAlign ="top") |>hc_caption(text ="Data Source: Dslabs")
Data set conclusion and insights
The data set I used was “stars” from the Dslabs library. First, I analyzed the data to find out what would make a meaningful visualization. I decided that comparing and looking at the temperature, star, and type of star would be meaningful. So, we could see if a types of star have a specific average temperature. I thought this would be best to see using an interactive highcharter line graph. I started looking at the basic layout, and finalized it by adding axis and legend labels, and the title.
An interesting insight I noticed was that type M of stars was the one we had the most data on, as well as having the lowest average temperatures. While other types like A or F, ended sooner. Additionally, there’s only one type O star with the highest available temperature, and it makes me wonder why there isn’t more of them.