Fix progress to avoid issues with type on iter number #39
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Start of torch backend * More torch utils * Most torch utils working * Got ePIE working on torch * Renamed cupy backend, generalizing dataclass * Typing fixes * More torch work, basic grads running * Gradient descent solver working * More solvers with torch * Add back in dtype checks * Implement affine_transform order=0,1 on torch * More device selection abstractions * torch fixes and improvements * Add torch optional dependency
* Fix drop_nan_patterns with tilt * initial setup * dm4 data at least loading, may need flips, etc * add flips after gatan read-in will need to move if in metadat * turned off memmap on loading for improved performance * fixed flipped (done by reader) * adding an offset hook * fixed an error * including a transpose * need to keep the mask * issue fix with scan shape * reading in the e- calibrations and appying to patterns * line cleanup * cleanup --------- Co-authored-by: jmlebeau@gmail.com <jmlebeau@gmail.com> Co-authored-by: subangstrom <lebeau@mit.edu>
…ay need to revisit this later
…ay need to revisit this later
* Add sign option to tree.grad() * Report granular/detailed losses Need to update conventional engines, as well as server/web interface * Granular losses for conventional engines * Fix web interface w/ granular losses * Typing fixes * Print detailed error breakdown * Hotfix for prepare_for_engine backend error
Owner
|
Can you make a PR to the develop branch instead of main? |
Collaborator
Author
|
Sorry, thought I had sent to develop
… On Nov 3, 2025, at 8:52 AM, Colin Gilgenbach ***@***.***> wrote:
hexane360
left a comment
(hexane360/phaser#39)
<#39 (comment)>
Can you make a PR to the develop branch instead of main?
—
Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMVFYVZR24HEE7IEWW6FOT325M3BAVCNFSM6AAAAACK7XBSR2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOBQHE2TOMRUGQ>.
You are receiving this because you authored the thread.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.