Skip to content

BiRefNet Portrait: exact checkpoint lineage and validation splits #323

Description

@BoazTelem

We are evaluating BiRefNet Portrait for commercial portrait cutouts and want to
record reproducible checkpoint provenance alongside its MIT license.

We saw your code/weight licensing clarification
and dataset licensing discussion.
The remaining questions concern the exact Portrait training history.

The artifact is ZhengPeng7/BiRefNet-portrait
at revision b6561965a70070d9143fd9e558f6ca3c481510db, file
model.safetensors. Hugging Face's LFS metadata reports SHA-256
4a4eb3a5469b75f0cccaec6772c22fc30e6c12ed429c2c0ba71b43e3d8d97182.

Could you point us to records covering these points for that exact checkpoint?

  1. Initialization and resume history: the training code revision, run config,
    and each initialization/resume checkpoint's source and digest. Did it start
    from a pretrained Swin backbone only, or inherit another BiRefNet checkpoint?
    The exported bb_pretrained: false setting describes loading, so we could
    not infer the original training history from it.
  2. Dataset versions and splits: the card lists P3M-10k excluding P3M-500-P,
    plus TR-humans. Does that include P3M-500-NP in training? Was P3M-500-P used
    to select the epoch, loss settings or other hyperparameters, in addition to
    reporting validation scores? Were any other data used by this checkpoint or
    its parent checkpoints?
  3. Synthetic-data identity: which TR-humans snapshot/archive was used,
    ideally identified by a digest or file list? Is there a record of its
    generator checkpoints and background-image sources?
  4. Applicable notices: are there checkpoint-specific notices or permissions
    covering the initialization weights, training sources and copied model
    components that should accompany the MIT code/weight license? Links to
    existing rights/provenance documentation would be helpful.

Thank you. A training config, log or model-card update addressing these points
would let us distinguish documented provenance from assumptions.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions