Open GuyAglionby opened 2 weeks ago
Hello Guy,
Sorry about that. Were you able to run scPRINT at least on a small test example?
DId the lamin login step worked? Lamin often asks for your a password at first login.
Be careful about the start_at=39
too. It means scdataloader will start at the 39'th dataset instead of the first (this is useful when you restart a failed run).
I'm assuming that this is because my username isn't associated with the cellxgene collection on lamin
I never had this issue on my end and I am not part of the lamindb team so I don't think this is the reason
I am thinking about one thing... you might need to create a lamin instance first: https://docs.lamin.ai/introduction#quickstart
# store artifacts in local directory `./lamin-intro`
!lamin init --storage ./lamin-intro --schema bionty
# (optional) make Django's unnecessary functionality private for clean auto-complete
!lamin settings set private-django-api true
Describe the bug + reproduction steps I'm trying to populate a database using the command in
__main__.py
. I'm using scDataLoader 1.1.3 and lamindb 0.76.3. A similar error occurs using scDataLoader 1.1.4, lamindb 0.76.9, and the 2024-07-01 cellxgene release.I've run:
The logs are as follows
I'm assuming that this is because my username isn't associated with the cellxgene collection on lamin
The relevant line of code in preprocessing.py is
edit: I thought the problem occured while processing
is_new_version_of
, but I tried commenting it and I still get the user not found error.(Also, I'm running this to try to construct the data needed to re-train scPRINT. Hopefully not barking up the wrong tree here but please let me know if so!)
Thanks in advance for any advice