gangstead

gangstead

This is my second year doing AoC in Elixir and my first year doing it with Livebook.

When I was doing just plain Elixir I usually set up each day as an exs script and ran it with elixir 2021-day1.exs 2021-1input.txt That way I could save the example input from the problem setup, and the user-specific input and switch back and forth.

@josevalim did it in livebook last year and I was looking at his code where he used Kino inputs (example) and copy/pasted the AoC input and ran it. This works great, but your input is not persisted across sessions.

I’ve tried reading a file from the Livebook, putting it in the same directory as my .livemd file and reading the file as file1.txt and ./file1.txt, but that’s not right. The file is not found. I’m guessing the path is relative to the livebook process, which might be different depending on how you’re running livebook (escript, livebook.app, or hosting it on a webserver).

Are there any other tips for reading a file from within a livebook? Whether it’s on the livebook server or from the browser with Kino, a smart cell, something else?

First 5 of 5 Posts Switch mode

stevensonmt

stevensonmt

maybe try using "#{__DIR__}/file1.txt" as the file path?

gangstead

gangstead OP

That works!

I’m still interested if there’s any way to do a file upload into a livebook. Maybe that’s a smart cell or something I could develop?

bmitc

bmitc

I am also using Livebook, and you can find my 2022 notebook here: advent-of-code/2022/elixir/advent_of_code_2022.livemd at main · bmitc/advent-of-code · GitHub

Warning: Solutions are there for days 1 and 2.

In particular, I am using a Utilities module to provide the data input file reading:

defmodule Utilities do
  @moduledoc """
  Provides utility functions to be used across days
  """

  @doc """
  Reads the given day's data file of "day_<zero padded day number>_input.txt" as
  a stream
  """
  @spec readDataStream(integer()) :: Stream.t()
  def readDataStream(day) do
    day_as_string =
      day
      |> Integer.to_string()
      |> String.pad_leading(2, "0")

    Path.join(__DIR__, "../data/day_#{day_as_string}_input.txt")
    |> Path.expand()
    |> File.stream!()
    |> Stream.map(&String.trim/1)
  end
end

I download all of the input files and name them as day_<number>_input.txt. For example, day_01_input.txt. I put them in a data folder up a level from the notebook because the intention is to potentially support several languages but keep the input files in a single location for a given year.

I also have tests setup to help in refactoring after I have solved a puzzle.

ExUnit.start(autorun: false)

defmodule AdventOfCode.Tests do
  use ExUnit.Case, async: true

  test "Day 1" do
    assert Day1.part_one() == # redacted
    assert Day1.part_two() == # redacted
  end

  test "Day 2" do
    assert Day2.PartOne.solution() == # redacted
    assert Day2.PartTwo.solution() == # redacted
  end
end

ExUnit.run()
mruoss

mruoss

I’m using kino_aoc. A very handy tool imo.

https://github.com/mruoss/advent_of_code/blob/main/2022/day04.livemd

netto

netto

Hey.

I use this SmartCell that fetches the puzzle and the input to a Livebook.

https://github.com/nettinho/smaoc

Hope it can be helpful.

— All posts loaded —

Where Next? Top

Trending in Challenges Top

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge &amp; Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
juhalehtonen
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New

We're in Beta

About us Mission Statement