JuliaApproximation / JuliaApproximation/ApproxFunBase.jl

Why won't `AbstractMatrix(::SubOperator)` return a `BandedBlockBandedMatrix`?

Open
#81 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Julia
Stars
13
Forks
13
Avg merge
10h 33m
Merged PRs (30d)
16

Description

I see that the line to return such a matrix is commented out below. Why?

https://github.com/JuliaApproximation/ApproxFunBase.jl/blob/25ee448cbde61ef8e01f5c9d5af63ac3364a751c/src/Operators/Operator.jl#L776

I'd like to preallocate large operator matrices and currently the RaggedMatrix type seems to be the default. The issue is that RaggedMatrix uses too much memory. Currently, I'm just manually using BandedBlockBandedMatrix, but that's not as nice as just being able to use AbstractMatrix(view(SomeOperator, FiniteRange, 1:N))), since I don't want to have to care about the exact memory layout myself.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at src/Operators/Operator.jl around line 776 and inspect the commented BandedBlockBandedMatrix return alongside the existing RaggedMatrix path. Trace how AbstractMatrix(view(SomeOperator, FiniteRange, 1:N)) selects its matrix type and determine whether the requested return can avoid excess memory without requiring callers to manage the layout; document the reason or implement the behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
julia
Domain
backend, performance
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.