diff --git a/LICENCE b/LICENCE index d98cad8d89a828427fa50a271dc8805bf73804fa..775f9ce3980f082c5c48b28e3f90686d20870552 100644 --- a/LICENCE +++ b/LICENCE @@ -1,20 +1,26 @@ The binary_c/nucsyn code LICENCE -------------------------------- -The binary_ code (also known fas 'binary_c/nucsyn') is based on the BSE code of Jarrod Hurley, as rewritten by Robert Izzard (RGI), with many new functions to follow stellar nucleosynthesis, among other things.Many parts have been rewritten in a more modular way, please appreciate thatthe many improvements are always a work in progress. +The binary_c code was originally based on the BSE code of Jarrod Hurley, as rewritten by Robert Izzard (RGI), with many new functions to follow stellar nucleosynthesis, among other exciting physics. Many parts have been rewritten in a more modular way, please appreciate that the many improvements are always a work in progress. -The (current) websites of binary_c are -http://www.ast.cam.ac.uk/~rgi/binary_c.html +The (current) website of binary_c is http://personal.ph.surrey.ac.uk/~ri0005/binary_c.html -The facebook page is +The git repository is at +https://gitlab.eps.surrey.ac.uk/ri0005/binary_c + +[when RGI moves job, this will move, but your search engine of choice will + still find it] + +Social media pages: +https://twitter.com/binary_c_code https://www.facebook.com/groups/149489915089142/?fref=ts There are two mailing lists on google groups, please join them: https://groups.google.com/forum/#!forum/binary_c-nucsyn-announce https://groups.google.com/forum/#!forum/binary_c-nucsyn-devel -To get the code, please email rob at r.izzard@surrey.ac.uk +We also have a very active Slack group. --- @@ -23,7 +29,7 @@ If you use this code, however directly or indirectly, and "this code" includes binary objects, modules etc. that go with it, and go on to use the results for any paper, poster, publication or distribution of information derived from, with or by the use of this code you must contact RGI at -rgi <_a_t_> cam.ac.uk (alternatively rob.izzard <_a_t_> gmail.com) +r.izzard <_a_t_> surrey.ac.uk (alternatively rob.izzard <_a_t_> gmail.com) to discuss whether you should add him to the author list or cite him. You should also contact Jarrod Hurley, since he wrote the original Fortran code - he may want his name on the paper too. It has @@ -32,7 +38,7 @@ it if you let him know you're using his code (by however circuitous a route!). Usually a citation will do, but you know, if RGI helps you a lot and you use his code extensively, it is polite to consider an author slot. You should -*at least ask*! +*at least ask*! (It also keeps him in a job.) If you are required to cite, then usually something along the lines of: @@ -96,7 +102,7 @@ Carlo Abate wrote the Wind-RLOF code and updated the s-process at low metallicit John Eldridge provided his tables of stellar colours for the stellar_colours library. Giovanni Rosotti provided help with the accretion onto binaries as f(q). Adam Jermyn has worked most on the discs code and his help is greatly appreciated. -Holly Preece provided the tables for first dredge up, as used in nucsyn_strip_and_mix and Izzard+ (2017). +Holly Preece provided the tables for first dredge up, as used in nucsyn_strip_and_mix and Izzard+ (2018). Also, thanks to Chris Tout, Onno Pols and John Lattanzio for advice down the years. @@ -104,15 +110,18 @@ Finally, by using binary_c/nucsyn you agree to: * Commit your ongoing work and improvements to the code to the main code repository. Your work cannot be private. -* That your work can be incorporated, as soon as reasonably possible, into the binary_c/nucsyn trunk (and hence branches of users) so that it is available to all binary_c users. You naturally have time to publish your work first. We're a friendly lot (in general!) and would rather work together than in competition. There is no point in reinventing the wheel! +* That your work can be incorporated, as soon as reasonably possible, into binary_c/nucsyn so that it is available to all binary_c users. You naturally have time to publish your work first. We're a friendly lot (in general!) and would rather work together than in direct competition. There is no point in reinventing the wheel. -* The LICENCE is subject to changes and/or updates. By continuing to use binary_c/nucsyn, you agree to the latest LICENCE terms (in the trunk), not those that came with your branch. Please regularly check the trunk LICENCE file for updates. +* The LICENCE is subject to changes and/or updates. By continuing to use binary_c/nucsyn, you agree to the latest LICENCE terms (as updated on the main git server). Please regularly check the LICENCE file for updates. -Look out for the semi-regular binary_c workshops. Check out the website for details. +Look out for the semi-regular binary_c workshops. Check out the website for details, +or visit the videos on YouTube +https://www.youtube.com/watch?v=vskIb_kt0C8&list=PLvEoX7AHHOBglXeT6lEQ-hgAJDt6iIrPj +https://www.youtube.com/watch?v=kmjM3FkTLSc&t=24s thanks for your time! -25/07/2007, last updated 22/01/2019. +Last updated 01/08/2021. ------------------------------------------------------------