-
Notifications
You must be signed in to change notification settings - Fork 152
Create Federated_Learning #1750
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,47 @@ | ||
| --- | ||
| title: Federated Learning Best Practices | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe a temporary working title, but I would try to follow our current title structure. What is the task that a researcher/data steward has to tackle, in the context of data management. I think we should also be careful this does not talk to much about software.
Collaborator
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @bedroesb yes it is a temporary working title. I have advised about the scope and context of the Your Task pages to the author. I'll be working with them to get it right. |
||
| description: <!---REPLACE THIS with a one sentence description of the page---> | ||
| contributors: [Jorge Silva] | ||
| page_id: <!---REPLACE THIS with a shortened page name. The shortened page name should be in lowercase and separated by underscore(s) if needed. For example, page_id of structural bioinformatics will be struct_bioinfo ---> | ||
| related_pages: | ||
| Tool_assembly: [<!---REPLACE THIS with the page ID of the tool_assembly pages that you want to list here as related pages--->] | ||
| # More information on which page id you can use can be found at https://rdmkit.elixir-europe.org/website_overview | ||
| training: | ||
| - name: | ||
| registry: | ||
| url: | ||
| # More information on how to fill in this metadata section can be found here https://rdmkit.elixir-europe.org/page_metadata | ||
| --- | ||
| <!-- Please take in mind our style guide https://rdmkit.elixir-europe.org/style_guide when writing the content of this page. --> | ||
|
|
||
| ## Concrete problem 1, formulated as a question <!-- example: what is the best way to name a file?--> | ||
|
|
||
| ### Description <!-- do not delete this heading and write your text below it --> | ||
|
|
||
| Short explanation of what this problem is about. | ||
|
|
||
| ### Considerations <!-- do not delete this heading and write your text below it --> | ||
|
|
||
| * [Structured in bullet points](style_guide#text) as much as possible, detailing things to consider about this problem in order to be able to find the right solution. | ||
|
|
||
| ### Solutions <!-- do not delete this heading and write your text below it --> | ||
|
|
||
| By using [bullet point style](style_guide#text) as much as possible, try to describe when, why and for what is best to use a specific tool or resource. | ||
| Avoid making long list of links to tools and resources. | ||
| Make sure to add the tools and resources mentioned in the text in the main "tools and resources" table. | ||
|
|
||
| * Bullet point solution 1 | ||
| * Sub-point | ||
| * Bullet point solution 2 | ||
|
|
||
|
|
||
| ## Concrete problem 2, formulated as a question <!-- example: where to find ontologies?--> | ||
|
|
||
| ### Description <!-- do not delete this heading and write your text below it --> | ||
| Same as above | ||
|
|
||
| ### Considerations <!-- do not delete this heading and write your text below it --> | ||
| Same as above | ||
|
|
||
| ### Solutions <!-- do not delete this heading and write your text below it --> | ||
| Same as above | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no capitals in the filename