Skip to content

Update Position#502

Closed
bam241 wants to merge 17 commits intocyclus:mainfrom
bam241:position
Closed

Update Position#502
bam241 wants to merge 17 commits intocyclus:mainfrom
bam241:position

Conversation

@bam241
Copy link
Copy Markdown
Member

@bam241 bam241 commented Jun 3, 2019

This follows cyclus/cyclus#1510.

simplifying the call to toolkit::Position

@bam241
Copy link
Copy Markdown
Member Author

bam241 commented Jun 5, 2019

apparently Position unit tests are missing for XX_insts and YY_regions

@bam241
Copy link
Copy Markdown
Member Author

bam241 commented Jun 5, 2019

this should not be passing before the corresponding PR is merged in Cyclus (cyclus/cyclus#1510)

@bam241
Copy link
Copy Markdown
Member Author

bam241 commented Apr 12, 2025

@gonuke I updated this.
rebasing was too complicated with all the "recent" change, I did a merge!

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 12, 2025

Build Status Report - 29642a4 - 2025-06-15 15:25:29 +0000

Build FROM cyclus_20.04_apt/cyclus:latest
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_20.04_apt/cyclus:stable
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_20.04_conda/cyclus:latest
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_20.04_conda/cyclus:stable
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_22.04_apt/cyclus:latest
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_22.04_apt/cyclus:stable
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_22.04_conda/cyclus:latest
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_22.04_conda/cyclus:stable
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_24.04_apt/cyclus:latest
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_24.04_apt/cyclus:stable
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_24.04_conda/cyclus:latest
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️
Build FROM cyclus_24.04_conda/cyclus:stable
  • Cycamore: Failure
  • Cymetric: Skipped due to upstream failure ⚠️

@gonuke
Copy link
Copy Markdown
Member

gonuke commented Apr 12, 2025

These failures are because we need cyclus/cyclus#1510 to be merged before these changes make any sense.

@dean-krueger
Copy link
Copy Markdown
Contributor

Now that cyclus/cyclus#1510 has been merged, does this need another look? @bam241 @gonuke @katyhuff

@bam241
Copy link
Copy Markdown
Member Author

bam241 commented Jun 13, 2025

I believe one should first rerun the ci.

I can push an empty commit if needed :)

@bam241
Copy link
Copy Markdown
Member Author

bam241 commented Jun 13, 2025

I triggered the CI to see if that's working as expected

@bam241 bam241 marked this pull request as ready for review June 13, 2025 19:41
@bam241
Copy link
Copy Markdown
Member Author

bam241 commented Jun 13, 2025

CI seems to be working, moved it into ready to review (from draft)

Copy link
Copy Markdown
Member

@katyhuff katyhuff left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good. I have a fussy set of style edits that add a space between function input parameters. Accepting these changes would be nice, but is not required for merging, so I will mark this "Approve" as far as I'm concerned (as long as CI tests are continuing to pass).

Copy link
Copy Markdown
Member

@gonuke gonuke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The initialization of the injected variables needs to be reviewed and updated (as necessary) to the patterns that we've used elsewhere

Comment on lines 8 to -10
latitude(0.0),
longitude(0.0),
coordinates(latitude, longitude) {}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we need to review/reconfirm the way that we do initialization of variables that are injected. We don't initialize other variables quite this way, I don't think.

@katyhuff suggestions

Co-authored-by: Katy Huff <katyhuff@users.noreply.github.com>
@dean-krueger
Copy link
Copy Markdown
Contributor

Hi @bam241, I spoke with @gonuke this morning about this PR and he mentioned that you had told him previously that you might not have a ton of time for it. If it's alright with you, then, I'd love to volunteer to try to get this over the finish line. I would, of course, request your input for review (though you need not give it if you're swamped) but before I went ahead and started changing stuff I wanted to ping you and double check that I wouldn't be stepping on any toes by doing so. Let me know whenever if that works, and if not no worries!

@bam241
Copy link
Copy Markdown
Member Author

bam241 commented Jun 18, 2025

@dean-krueger find by me,
I'd be happy to see that completed.

I sent you an invite to my cycamore repo, so you can keep this open.

If you prefer opening an new PR, do as you wish :)

I am not "swamped" but I didn't work on this for long time, it is time consuming to go back into this :)

If you need anything, ping me

@dean-krueger
Copy link
Copy Markdown
Contributor

I think the position stuff just got merged from my branch today by @gonuke, if you're fine with it, I think you can go ahead and close this PR @bam241 ! Thanks for all the work on this you guys, I'm really glad this finally got across the finish line.

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

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

4 participants