Turing REG EDI SA
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Help
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    > Questions marked * MUST be completed. ## Section 1: Background ### 1. Project appraisal meeting* > Link to the relevant [milestone](https://github.com/alan-turing-institute/Hut23/milestones). ### 2. Project proposal name/working title* ### 3. Brief description* > 300 words max. If this is an extension of an earlier REG project, provide Project Tracker link and highlight main results achieved. ### 4. Project Tracker issue link* ### 5. Principal Investigator(s)* ### 6. Earliest possible start date* ### 7. Latest possible start date* ### 8. Earliest possible end date* ### 9. Latest possible end date* ### 10. Estimated project duration (months)* ### 11. Reviewer 1* > REG lead who conducted the scoping meeting and produced the brief. ### 12. PMU contact* > PMU person who attended scoping meeting and completed Funding section below. ### 13. Partnerships team contact* > Relevant partnerships person who attended scoping meeting, if project is funded through a partner grant. Use N/A if not applicable. ### 14. Reviewer 2* > REG Senior who agreed to review the brief. Use TBD if still to be determined. ### 15. Conflict of interest* > Mention any potential conflict of interest, and actions taken to avoid it, that should be noted when discussing the brief (e.g. the REG lead who produced the brief is a project Co-I). ## Section 2: Relevance* > Describe how the proposal aligns with the REG project priority criteria (max 300 words for each). Refer to REG [project appraisal criteria](https://github.com/alan-turing-institute/research-engineering-group/wiki/Criteria-for-project-appraisal) for further information. ### 16. Impact* ### 17. Diversity* ### 18. Pioneering* ### 19. Openness* ### 20. Alignment with Turing 2.0* ## Section 3: Staff* ### 21. What specific skills should the requested staff possess?* > Enumerate any required skills beyond generic RSE/DS skills. ### 22. Preferred level of experience of the requested staff* > List all that apply from the following (or _Any_ if there are no constraints): > * Junior: 0-3 yrs post-PhD experience, or 3 yrs experience if no PhD > * Intermediate: 3-8 yrs post PhD experience, or equivalent > * Senior: 8+ yrs post-PhD experience, or equivalent ### 23. What does the work expected from the requested staff consist of?* ### 24. What is the expertise of the other members of the project team?* ### 25. Any specifics concerning the working place or working patterns* > E.g. project team location; opportunity for remote collaboration; compulsory week days in the office. Enter _None_ if there are no constraints. ### 26. Estimated effort requested (in multiples of 0.5 FTE)* ### 27. How flexible is the requested FTE?* ### 28. Could the work be done jointly by REG and a delivery partner?* ## Section 4: Funding ### 29. Is funding for this project available?* > Depending on your answer to this question, complete **either** Section 4a **or** 4b. Yes – not 100% confirmed yet but we expect it will be confirmed before Christmas 2022 ### Section 4a - Funding available > If funding for the project is already secured, the following questions are **mandatory**. <details> ### 30. The funding body* > If a research grant please provide the Research Council and award number. Lloyd's Register Foundation via York University ### 31. If Turing funded, specify the (closest related) Turing programme* ### 32. Amount of the approved budget* £74,236 ### 33. Rate of overheads paid* No overheads paid ### 34. Mention any funding flow-downs likely to require legal input* > E.g. IP arrangements, restricted publication of outputs, staff employment conditions. We are currently reviewing the contract and will update when we have more details on this. We expect that the work will comply with Turing’s open research outputs policy. If we decide to use a delivery partner we may need to double check the terms around consultancy. ### 35. Any other T&Cs that may affect the project but are unlikely to require legal input* > E.g. date by which funding must be spent. Funds must be spent by 30 September 2023. Project needs to start in January 2023. There is flexibility in how the funding is used during this period (up to 1.0 FTE for 11 months). </details> ### Section 4b - Funding sought > If funding for the project is not (fully) secured yet, the following questions are **mandatory**. <details> ### 36. What plans are in place for securing funding and what is the current situation?* ### 37. If a funding application is being submitted, when is the application deadline?* ### 38. When is the application outcome expected?* </details> ## Section 5: Supplementary Information ### 39. Project documentation, if available > E.g. case for support if the work emerges from RCUK funding. ### 40. Additional background reading, if available > E.g. research papers. ### 41. Any software languages, frameworks, libraries tools and platforms you expect the project to use*

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully