 Okay so hello everyone I'm Aniket Pradhan. Am I audible over there? It's fine. Yeah, good. So I'm Aniket Pradhan and today I'll be talking about neuro Fedora and how we can use, I mean like about neuro Fedora what it is and what's the aim and motive behind it and what's what's the purpose of like actually having a neuro Fedora thing over here. So I guess like everyone would be aware of Fedora what Fedora is. So Fedora is just another operating system based on Linux just like Debian or Ubuntu. So neuro Fedora is a group that's main purpose is to provide neuroscience packages, neuroscience software in Fedora. So before we dig into dig deeper into neuro Fedora just start about like how do we do our research in neuroscience in the neuroscience community. So the research pipeline basically. So I mean as you can see in the diagram it's actually a simplified diagram but it's actually quite complex process. So I mean it's the general overflow I mean like we go from data analysis to theory and then we have like modeling our neuroscience or any neuroscience structure and then we have our experiments and stuff like most of these works nowadays are being conducted through the use of computer software and computer tools. So like there are many tools like for experimental we have like EEG monitoring and stuff and like we have CD machines we have MRI for data analysis we have statistical machine learning libraries and data analysis like NumBuy, cyber I mean like Python libraries I mean and then we have theory and modeling softwares there are all kinds of simulators. So I mean like there's a list of like all kinds of all kinds of tools and softwares that we use to like produce and reproduce information in the research domain that's like we need softwares for visualization, academic writing like LaTeX and I don't know any other sort of LaTeX but yeah we have non-academic writing like blogging and we use software for podcasting and stuff and so on and so forth okay. So what do we mean by free and open science okay so I mean like free and open like everyone should be able to like have the freedom to share read or make amendments and modify to your scientific material right like that's the definition of first everyone should have access the should have freedom to access and study what you are actually working on right so okay let's move on forward so over here it's about it's a paper by P. Gleason about a commitment to open science in neuroscience it's basically its main motive is to solve the reproducibility crisis that we have like we're unable to reproduce the data or the results I mean like that's very important if you are publishing some papers or your results on on to the public so like what can be the benefits of having open source codes I mean like it can first of all solve the reproducibility crisis like people can reuse that code and then build upon their new tools and software on it and the publication or the code becomes an advert for each other I mean like you go to a publication people will look at your code you go to the code people look at your publication and then you can go on forth with developing new stuff so neuro Fedora why so I mean like the neuroscience community is full of I mean the scientific community is full of people from different domains I mean not everyone over here is a software developer right I mean that most of people most people are biologists or some data analysts or some not everyone is a software developer don't add not everyone has the required experience right so only a small proportion of the scientists or the actual people working on research are trained software developers so they work on the software and they create they create they are basically developers of the software tool they create us or they create a tool that can be used by the end users but the main problem here is that the developer may not provide like proper instruction on how to use the tool I mean he may not provide documentation and there are some people the end user and like the end users they are not necessarily they are not necessarily trained software developers so they may not have the required knowledge they might have the required knowledge or the experience to build and use the tool directly and over here the end users may not always provide the feedback on how good the tool is if it's working correctly or not so if you are a developer I mean neuroscience tool developer then like we often face many of such problems like there's often a single developer a single professor single professor who's working on a single or a small team who's working on a single development tool so and like given how interdisciplinary in the neuroscience community is most researchers are not trained in development so I mean like we have limited maintenance or short-lived projects because once a research work once our research work is done like people no longer contribute to it and they have limited access to hardware limited code quality and like based on all these evidences like software used in research is not always of the best quality may not always be of the best quality so I mean like it may or may not mean the development standards that people in the programming domain have like the proper developers who are trained in software programming and all so and they have complex dependency change there can be some dependency loops as well but like how can how can a developer solve that so that's the problem in the software in the research domain right now but for the end users like many of the end users they waste time and effort to install your the whenever they waste time installing a particular tool they have to go through the particular tools dependencies and then resolve the dependencies first and then get the tool right there is lack the required skill of programming usually I mean like not always but yeah they have a hard time setting up and using the software they rarely send bug reports upstream and they do not check for tests I mean like they do not run the test with so how do they ensure the correctness of the working program I mean testing the correctness of a program is very important in the research domain in the academic domain that's to ensure your final paper's correctness and many of the end users are unaware of the help for developmental tools like many of many end users do not know that there exists a library to analyze your die-com files and everything but instead they do it manually so that's what that's where neuro fedora or this where distributions come in so what basically distributions do is that they take the code from the developer and then they package it in a neat and nice way and then provided it to the end user so the distributions like fedora or debian they act as a liaison between the user and the developers they provide the feedback and report bugs to the developer as well and it basically simplifies your installation and your usage of any software tool that is being packaged so I mean like distributions like fedora they have a good advantage at being over here they have high end servers they have like multiples multiple mirrors running across the globe and they have you have the infrastructure and they are like firm packaging guidelines follow the best practices we always run the test suits and we before a tool is packaged it goes through a heavy duty review process so I mean like the tool is properly tested and then it is provided to the end users and we constantly work on community development we learn from one another and we always provide help to the users so that's where we come in so neuro fedora what it is it's a group of people who are aiming to package your neuroscience tools and software for the fedora operating system so our primary goal is to provide a ready to use integrated force platform for neuroscientists right so we aim to create a spin or a lab image of your fedora and provide it to the users in fact we have created one and we will share it to you in the next few slides and our secondary and secondary goals is to improve the standards of packaging and maintaining the tools help users develop help users develop the software development skills that are required for when you are creating a tool or when you are using it and make neuroscience accessible to non-specialists right so our neuro fedora our current metrics we just turned a year old in september 2019 we have like 20 volunteers 16 packages and only five who were from a neuroscience background so most of us are just acting as packages while those five are actually guiding us on how to package and how to review stuff we have five designers and newcomers as well so sorry so about software we have like 135 tools we have packaged for fedora right now we have like the neuron simulator the nest simulator genesis brian moves and we are we have like multiple packages in queue as well we have around like 180 packages in queue like some sorry sorry yeah so we have like 180 packages in queue that are being that that are in process of being packaged and stuff so we have neuro mlite and simulators of that kind as well so I guess that's it this is the current slide I mean you can search us on google and you can search you have a mailing list over here as well we have an irc channel a telegram channel as well our documentation is present at neuro dot fedora project dot org we have a blog as well please do have a look at it that's it for me so any questions people may have regarding neuro fedora over here yes please can you please read the question I mean like all the packages that we are creating right now okay so okay yeah so the question is if we are creating a separate repository for fedora this upstream is separate from the fedora repository right so the upstream is separate from our fedora repository I mean we are creating our own packages and they are getting stored in the fedora servers the upstream is separate from it we just take the release turbo or the release zip from the upstream and then use it as our source code and then we package it in a nice way and then we provide it to the end users so it's all separate right please coming from the scientific background uh coming from the scientific world yeah so uh his question is uh what does the fedora core team think of uh the packages coming from the scientific world so um I don't have any views of that what the core team thinks of the fedora core teams think but we as a group think that each and every like uh software can like can be from many any domain like either be scientific or video or multimedia so that's a perspective that uh we want neuroscience packages in fedora so we formed a group we want like neuroscience packages and the fedora the community is very welcoming the core the core team they actually support us for including the packages in fedora sorry for I'm about to throw it right now anyone any questions any more further questions I guess that's it