Opened 19 months ago

Last modified 5 weeks ago

#30090 new enhancement

Implemented test function for BIBDs

Reported by: gh-Ivo-Maffei Owned by:
Priority: major Milestone: sage-9.6
Component: combinatorial designs Keywords: bibd
Cc: dimpase Merged in:
Authors: Ivo Maffei Reviewers:
Report Upstream: N/A Work issues:
Branch: u/gh-Ivo-Maffei/bibd_tests (Commits, GitHub, GitLab) Commit: 675378180b8201601fcfa15226a0a2dcd7c7a2f1
Dependencies: #30037 Stopgaps:

Status badges


Implemented a function to test the recursive construction given in the method balanced_incomplete_block_design.

Change History (8)

comment:1 Changed 19 months ago by gh-Ivo-Maffei

  • Cc dimpase added

This function takes in a maximum value for v and a range for lambda and then tests all possible BIBDs that can arise from the recursive construction. I'm not sure if this is what you meant, or if you were thinking at a more general function.

comment:2 Changed 19 months ago by dimpase

I meant testing every construction available, as if you build a full database of (v,k,l) for which Sage does/does not know how to build a design.

comment:3 Changed 19 months ago by git

  • Commit changed from 5982cc82749c77d5193de24a8b4a50c4a05361ce to 675378180b8201601fcfa15226a0a2dcd7c7a2f1

Branch pushed to git repo; I updated commit sha1. This was a forced push. New commits:

aa99d3eadded a recursive construction
d137495fixed bug; added tests
f689565added function to test recursive construction
6753781skeleton of test function

comment:4 Changed 19 months ago by gh-Ivo-Maffei

I rebased the branch to Sage 9.2.beta4. I know the docstring is wrong and the function now doesn't work (see #30102), but I would like to know if this is a good structure for the function.

The idea is to test whether Sage can build the BIBDs Sage claims to be able to build, then to test that there are not parameters that Sage is able to build but claims it can't.

It should be a quite comprehensive test, but it feels like the second part is going to be hard to maintain. I'm not sure that's the best approach. I'm not sure how much I should trust sage and the existing code and how much needs to be checked in the test function.

comment:5 Changed 15 months ago by mkoeppe

  • Milestone changed from sage-9.2 to sage-9.3

comment:6 Changed 11 months ago by mkoeppe

  • Milestone changed from sage-9.3 to sage-9.4

Setting new milestone based on a cursory review of ticket status, priority, and last modification date.

comment:7 Changed 6 months ago by mkoeppe

  • Milestone changed from sage-9.4 to sage-9.5

comment:8 Changed 5 weeks ago by mkoeppe

  • Milestone changed from sage-9.5 to sage-9.6
Note: See TracTickets for help on using tickets.