-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
infant_recon_all
does not guarantee reproducibility
#127
Labels
bug
Something isn't working
Comments
was there an update on this? i also see this message but i'm not sure if it will affect the output? |
AFAIK, there hasn't been any updates to |
Hi All,
Our update was delayed due to some staff turnover, so no updates have been made. Hopefully coming soon though.
Let me know if you have any other questions.
Lilla
…________________________________
From: Mathias Goncalves ***@***.***>
Sent: Thursday, April 4, 2024 9:15 PM
To: nipreps/nibabies ***@***.***>
Cc: lillazollei ***@***.***>; Mention ***@***.***>
Subject: Re: [nipreps/nibabies] `infant_recon_all` does not guarantee reproducibility (#127)
External Email - Use Caution
AFAIK, there hasn't been any updates to infant_recon_all - I haven't inspected the log in awhile but it's possible the seed used is logged there, perhaps @lillazollei<https://secure-web.cisco.com/1DCN9vOrATWA2jT0AIVCI8f-KTOs0V50Shia448Q0YBDtalTFnZ5kN50RDry5MX-e4fHTJTUgh9GtiZkOjiG16gD2u0AflnliBPplSb01THt493ZXkvXQGr2lg1yzG8r628j6GZH-TjMAgZi45k3r2Ip1nbscva3XgJvVlHjy8OlT0Pob9rIi3KUKjuYlWamu9LCi6n_sLulH4_li7tExvEQrzC4ugerlOT13EeQFOKZJaLiaXMm2oer1ajUlHOSlJGn-LKM6nXbDMlPSLvuw8IpVNgIKZaeCWM8PrlCnLMn1k8L1bfOgWC_FDgEqTDU2/https%3A%2F%2Fgithub.com%2Flillazollei> may know
—
Reply to this email directly, view it on GitHub<https://secure-web.cisco.com/1SYC2tOdgCcjU_NHp9uBPdVzyvq2nvKdLat42K8wR16TIKeNr7WoyremAynPLEiQjiW4tzQ_ZHkTsv5YN5R1wWtw_SKXKj1oWAgJj-r-_JGARfQthEs-cssAuy4Wp1Yw_wk6Wpn30FBLfl4i1JYA0jnnq7FA2Gm8v42Al8PH2DqRzOSKyUj5yEQF0wcivQzIT5z6ZC0pi_9E_wLdnefyjVgOV5GJm2w9vKrDauPiBKA-GK-B4x6hSLrC5fgWyT6Opof9IIzRjME5TfoXtkuMA0APcBcqQvhGnE7Lti5A0JRS5yKxE7HoLEkJVPBO3xzgF/https%3A%2F%2Fgithub.com%2Fnipreps%2Fnibabies%2Fissues%2F127%23issuecomment-2038573042>, or unsubscribe<https://secure-web.cisco.com/1N8g5dmbuvWs0hpMitRa1Qi-N10ZsxhyGZ7UzS-FYCeckeDdOvs-bZnbxgu0n7KsRcXHrkqLBIymOPNaTIK27qqetu_B5qd6QNt6tCCgBo-Cd10lXQ-FYdxnJdTom7sBcebsQql836t7o8utEbQVWz9n7b0zjCZXtTs6L4l9idud9AOJHTmYy3867GcSJZ8Xc0kJXCC6jCu9H6ANwBxa6l5A-dQ9ItNq_bGItQTHJfRmF5_MKoCS9Dt4IY_daV6OegEKBz52ARWNipfa8c1osevUmZEY8fT0Dbvoef-3NFyZC3VA1H4NnDTL_xPf-zSb5/https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABRMDIMDP7EG6KZW3QDWDEDY3X3KFAVCNFSM5FUDFHXKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBTHA2TOMZQGQZA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
[ { ***@***.***": "http://schema.org", ***@***.***": "EmailMessage", "potentialAction": { ***@***.***": "ViewAction", "target": "#127 (comment)", "url": "#127 (comment)", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { ***@***.***": "Organization", "name": "GitHub", "url": "https://github.com" } } ]
The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient information, please contact the Mass General Brigham Compliance HelpLine at https://www.massgeneralbrigham.org/complianceline <https://www.massgeneralbrigham.org/complianceline> .
Please note that this e-mail is not secure (encrypted). If you do not wish to continue communication over unencrypted e-mail, please notify the sender of this message immediately. Continuing to send or respond to e-mail after receiving this message means you understand and accept this risk and wish to continue to communicate over unencrypted e-mail.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
Looking through the
infant_recon_all
log, this line pops up a few times.What command did you use?
Version
21.0.0 release candidates (rc)
Relevant log output
No response
Add any additional information or context about the problem here.
cc @lillazollei
The text was updated successfully, but these errors were encountered: