Thanks. Nice to meet you everyone. I really like this introduction. I think we should start with introduction. It doesn't matter if we are 50 people next time, but I think it's a good way of starting, because I liked learning about actually what you do and understanding how aware you are or familiar you are of Vargos. Today's meeting is very casual. We don't have much to present. We would like to inform you about what's coming next month, so about four core functionalities that are coming in Argos and about an event that is coming that you can also participate. But before doing that, I understand that some participants would like to know more about Argos, so maybe I can quickly demo the very simple, let's say, flow of creating your DMP in Argos. So let me quickly do that. First I need to share the correct window. It's wrong, right? No, it's not. Can you see the screen? I don't know what you're saying. Yes, yes, we can see it. Yes. Argos, right? Not the other one, because I have Yes, we can see Argos.ovenero.eu. Okay, good. Right, so this is the landing page of Argos. You can have a look later. We are working with my colleague Maria as you saw today. We're working on redesigning this website, so we will have a new landing page during before the summer, around the summer. But for now, if you want to enter the tool, it's by clicking the start your DMP or the login, and then there are different options to choose to log in from. You do not sign up in Argos, so we do not store any passwords and nothing, we just borrow them from external providers like Google, like Orchid, so we take your credentials from there. And the tip is if you want to log in with your institutional account, sorry, credentials, then that is possible if you select opener. And then you will be redirected here. And if I choose another account and choose to sign in with Edge again, then I can search my institution that was already with Athena. I can search my institution and add my credentials and login with my institutional credentials. So this is something that a lot of people ask, how can I do it? This is how you can do it. So if you're not logged in, you can still use, I mean, browse Argos. Mainly you can browse the public DMPs that are available from other colleagues in working in different domains. They have shared them openly. You can find them here and you can also check them on ZNoro, download them and, you know, consult them. Also, you can see the descriptions for the different outputs that they have created, that these are associated with these plants, these DMPs. So let's go to home and let's actually login. Victory, I will use Google for me because I have everything synced there. And now I can see more possibilities. I can see that besides of the public dashboard with plants and descriptions, I can also see my activity, my dashboards, my plants and my descriptions. So you notice that we don't, we are moving away from using the term DMP because we see that software management plans are also popping up and even other types of output are requested by policies or are encouraged by communities to be described in the DMP. So because the DMP purpose is expanding to support different types of outputs and activities and actors, that's why we have, we're moving away, as I mentioned, from referring to DMPs to referring to them as plans. And for us, a plan might have a description of a data set, a description of software. Both of them, only one of them, it doesn't matter. It depends on the needs of the research project. So it's very versatile how you want to use them. Right, so here you can see my dashboard. I have some plants with the descriptions of its plan inside. And if I want to create my own, I click start new plan from here. And I choose start wizard. The import from file is very advanced. It's a specific modification of an JSON file that should be read by the, by this import mechanism so that it's uploaded. So it's very specific to RDA, common standard in particular. It's not used commonly because you need to structure the JSON file according to this specification. But if you want to start from scratch as you would normally do, following the steps and answering the questions, you click start. And then for those of you who have used it in the past, you see that this screen has changed. This is not a screen that redirects to many, many fields as we had before. But it's a common, let's say, screen with two fields that ask for descriptive metadata of the DMP. So title, plan, description of plan. And once we give that, we select the type of blueprint we want this plan to have. The blueprint is the structure of the whole plan. So if we have, if we have a project that should have descriptions for both software and data sets, for example, then we create a blueprint that combines both these plans, software management plans and data management plans. And you can select this blueprint, let's say from here, this is a good example, Chisterra. Chisterra is a consortium of national funders funding ICT projects in Europe. And they have a good example of a blueprint that combines both software management plans and data management plans. So let me use that and click next. You see that the structure that the blueprint has is, has some basic information about the plan, the license, because we want at the end, the DMP to have a license so that it's applied some of the third principle so that it's findable, accessible, reusable. And to be reusable, it should have a license. We recommend the creative commons, the creative commons for CC by attribution where others can reuse our DMP, but we get acknowledged for sharing it openly and having it available to others. We can add funding and we have two sections where we can describe the content regarding data since software. So let's, let's take it from scratch though, from the start, sorry. I gave the title before and the description of the plan before so it's kept, it's prefilled here. I can add the researchers that are going to work on the DMP. So these are, for example, we will say and I can find them with their orchid. I can search them with their orchid or if I cannot find them with the orchid I can insert manually. Maybe they have a researcher ID or other identifiers and I can add them here. Same with affiliations. I can select from the list of sources that we harvest from open air and for example, select thinner, if I couldn't find it again, same thing, insert it manually. Change the language if I want to write the DMP in a different language. And when I invite my colleagues to help me with filling this information of this DMP then this will become, this contact field will become a dropdown where I can select which of those invited colleagues can serve as the contact point for this particular DMP. So now it's me because I haven't shared it with anyone. I'm the only one. I'm the owner and the only person that has access to it. But if I share it with all of you then this will become a list with all of you and I can select who is going to be the contact point. License. I gave a license to my DMP already, oops, sorry, already. And access rights is, again, we want others to be able to find the DMPs so that they can see, they can get the whole picture of the management activities, research management activities in the project if it's available. So if we're not talking about sensitive data, for example, sensitive information, sorry. We keep it restricted as we write the DMP and if we want to open it up to others we choose open access. So for sure before depositing the DMP we recommend to switch to open access. When you switch at the same time the DMP becomes available under public plans as we saw before and when it's deposited it's openly available like this to others so that they can download and check the metadata. Under funding we just add the funder and that will be Cistero for here and the grant from Cistero so which project that this grant for the project. If I cannot find it again I always have the option to insert it manually. Let's save it just to be sure that nothing will be lost. And then moving on to the fourth to the fourth section is where I can start adding content for the datasets of the project that will be produced, reduced or collected. If I click add then I have the option to pre-fill or manually insert information so pre-fill for example hopefully this will be the trick. Yeah this is from the API that we are using. Okay so pre-fill would pre-fill this the title description and some content but otherwise you can always manually add it title of dataset description about the about the dataset you can add some tags and when you select the template again just to verify then the whole content appears so you can see that this these are the sections that are asked for me to answer one to seven and I can start answering them by selecting from you know drop-down lists from adding narratives making hyperlinks even oops making hyperlinks point to extender's references and I can start you know also reading the instructions or guidance that might be available under its question and answering and then when I'm ready I can save and close and I can continue with creating more descriptions for more datasets or dataset collections or I can also if I have a software go to the next section do the same for a software that I'm creating so add basic information like title and description of the software and then move on to again answering questions for the software management like if there's documentation available and other relevant testing and to reproducibility and to interoperability questions and when I am ready I save it and I can see everything under my plans there it is and I can export it in different formats pdf document xml and rda json this is very specific to the rda standard that we are using so that the dmps at the end so the plans at the end this this at the end is interoperable add a new description at any point invite more people to like my colleagues to help I can invite Maria for example and give her owner co-ownership to edit this dmp or member does to view and I can clone the dmp event if I want to repurpose some of the parts of the dmp like the software or the dataset so maybe I want to repurpose only the software check this and I save it and then that this new dmp has only the the software description and nothing else and if I go back again I can see I can continue editing I can add more descriptions I can finalize it start always a new version of my dmp which is linked to the one that I already created so if I go back now I see two versions 0 and 1 and they are linked okay and I can finalize it I can finalize for example maybe the dmp with only the software submit it and if I click deposit now provided that I have of course all the metadata completed during the writing process I click deposit select Zenodo and the possibilities are the options are two logging with Zenodo if you have your credentials which we recommend because this will this means that you are also the author in the Zenodo record or use our credential to push this information to Zenodo so either we do it for you with a token or you do it with just logging in with your credentials and then I don't want to push anything now but we saw before and already ready version so when I click deposit then immediately I have this this box with the EOI and I can visit what I created which is again we've had that already open this this is how it works maybe we have questions from people but it's the first time looking at how are this works I have no question neither in the chat or in the google doc however maybe Ali we can clarify the different usage of Argos between researchers and administrators yes there's also the possibility to create your own blueprints templates and structures basically of how you want the plan to be at the end with which questions content and order of sections and everything you can do it but you need more rights you need to be admins as you said Julia and for that when you do that we will give you access and you can see all I mean you can see this new functionalities that appear when you're an admin or a template editor even and you can start with creating your own template and yes it's I don't know if I should now go into this demoing how the admin works but we have yes Monica and I ask about the then how to sign in and if for like researchers in certain institutions can they create their own account or how does it work no that you don't sign up to Argos you just sign in so if you want you still see my screen right yes okay good so if you want to use your institutional credentials then you click on the opener let me maximize that you click choose another account sign in with edge again and then it's signing in you know finding the institution that you want from the list and selecting it and then adding your credentials okay here I need to work to see if it works for us if it doesn't we should configure we should change some configurations yes we we receive yes we are doing that for other institutions as well thank you thank you in the case you have um unit help you can write to the appdesk dot open air dot to you and just to say that we are going to have this maybe that's a good opportunity to say that we are going to have a new release of Argos uh next month probably late uh april early may uh because we want to have some run some good tests on it and you will have more you will have a different login page but you will still be able to log in with your institutional accounts and credentials and we will we will have another community goal where we'll go through every new feature when this releases up but for what's coming now you saw what's there today but for what is coming let me switch can you see still on my screen with the mentee yes oh good perfect why don't I see okay then I created a mentee um where I'm just for fun uh you can the presenter move okay thank you and I have added like four let's say functionalities that are coming next month to which I'm going to tell you what they are going to be about and so how they will enhance what we already saw today and I would like your feedback not me only but the whole team would like your feedback because we still have time to make changes so if we if you want something to be seen in a particular or made in a particular way we still have time to modify things before we release everything so a lot of people have been requesting reviewing options so they would like to be able to review a dmp and not just edited and and we have been receiving we have been collecting all this requests and now it's the time we have worked on a reviewing functionality where you will be able to as you write the dmp to also make comments as annotations let's say to a specific point in the dmp that you want for example question one about data formats you can make a comment there and give you know your feedback to the dmp authors about what they could do to enhance maybe use more open formats and so on so we are going to have this reviewing functionality and yes we want to know your thoughts do you think this is something that will help you as well were you part of the group that requested it it's good to know and how would you like the reviewing to be should it be a different screen for example should it be embedded inside the argus area where we saw before that you can where you write your input how would be more convenient you can maybe i did something that i don't know no this is you looks like you need to moderate the questions but there are no questions right oh enable questions okay enable comments okay now i think i enabled them sorry did i can you write okay let me say test okay i wrote the test but nothing is up interesting i think i should change to another story it's the first time that i'm also using this moderation thing why did i do it like that anyway can i choose who can be a reviewer so we split it's a proof first so that we all see it okay okay now i know how it looks good so the question is can i choose who can be a reviewer and yes you can choose it during the invitation so you saw where where i clicked invite and i invited my colleague maria to join me in writing the dmp i i had only two options so this option will be enhanced and you will have a reviewing also option so there you can invite people that will become the reviewers this is um yeah this is how the functionalities for example do you want to see um where would you like to see a history of the comments left would you like to have a dedicated space inside argus where you see everything would you like to who should be able to resolve even the these comments is it only the owner is it the co-owner so people invited with editing rights do you mean something like a github revision in which you can suggest the revision or like um like some publication venue when you have a letter from a reviewer that is like next to the venue and you can read what the reviewer is saying yes like a word document for example what you open and you find the comments but then they disappear right do we want them to be like that for example in word if you resolve them and delete them then they disappear do we want the same here do we want to keep them somewhere i think it's interesting to have a reviewer um that can be uh i don't know the supervisor i could leak or even outside the the group but it also depends if the reviewer should be the project officer for instance mm-hmm so yes it depends correct how can i decide who can be uh the project officer cannot do their perform the review on argus i mean they they want the an exported and file you know an exported form of the dnp okay so the question could be after uh if i received the comment from the project officer uh and maybe at the first time i'm not asking a reviewer um then after the second the second dnp revised can i ask in that moment another reviewer you can ask he he can invite reviewers at any time this is what you mean yes yes at any time it doesn't yeah it doesn't matter yeah okay okay let me move on to the next so again we have been receiving some requests for the email notifications that we send when a dnp or a plan such as Manson fund or whatever it is uh is updated so when you update it you receive notifications and the whole team actually uh every time you click save we have minimized that in the past but what we are going to do now is we're going to collect all these notifications and instead of sending them via email we're going to introduce a notification space in in in argus this is what in app means so in the argus you will have a bell where you can see if there are new notifications and then if you click it you will be able to see all the changes performing different plans that you are either the owner or the co-owner or the reviewer and for the dnp or the plan for any of your activity inside argus and and we're going to keep the email notifications sent every we're going to see every day is the last discussion that we had we're going to see the every day at the end of the day a summary of the new changes happened in this plan do you think that this aligns with your with your needs as well is it better to have this option to have inside argus notification you know the bell click it see what what changes instead of receiving emails i'll take that as a i'll take this as yes and i'll move on to the next okay the pre-filling functionality currently is been enhanced and that's why we couldn't use it fully today um because uh because um what you will be able now to do is select from which source you want to fulfill the dnp uh actually a particular section of a dnp so for example if you have a section and a template that is only about ethics and you have and you have a source inside your institution maybe that you want to connect to this dnp you have a source where you keep this ethics report let's say inside your cms your system the universe system we can use this form to pre-fill already the dnp with some information around ethics that are asked in the dnp so we can start making these connections with other um sources both sources from repos like repositories for example that we can link the data set and get the metadata of the data set to pre-fill parts of the dnp or even an ethics report for example if it's available uh we can also do that and since i mean until the day the pre-filling functionality works only for repositories and this is changing so if you are an admin for example on argos you will be able to select each time which source you want to pre-fill to use to pre-fill the dnp with information maybe from other departments across your university and then lastly i think it's a fourth right we have we'll have no detentancy a lot of our you know our users and maybe you also have been requesting their own space inside argos.opener.eu but their own space also not only in terms of storage but also in terms of look and feel so for example they would like to be able when they log into argos.opener.eu here to see um well let's say here maybe because the landing page will be same so when they log in with their institutional account as we saw before they want to be able to see different things for example a logo of their institution somewhere here wherever different fonts different different colors even so different things maybe the terms the about the glossary the terms to be also in their own language and they want to also be able to have control of this the activity that the researchers that log in with the institutional credentials to see what are the plans that they create to to be able to you know have more control of what's happening in this space that is now tailored to the institutional needs at the end that means that instead of also if you are a tenant in argos that means that at the end instead of choosing a nodo you might want to configure and link to your own repository so that the dmps are exposed to your own repository and are linked to other outputs that you have there so these are all things that we took into consideration when talking to to you not only during the the calls the community calls but also offline in the the help desk the request that we receive in the help desk and we're going to introduce this multi-tenancy so whoever wants to have their own space and look and feel and configurations on argos to for example switch from the nodo and configure their own or create their own blueprints with their own prefilling configuration and their own templates they are able at their logo or do whatever they want they will be able to do it with this feature and yeah do you think this is something that speaks to you as well I think I should have opened it sorry I now see what I did now you can write right yes we can we we can write questions it was open okay no worries new new features on menti also so I'm getting myself familiar with them is it and do you think you will use it more as it is with the zenn nodo configuration for example I let's take this as an example or or with customization does it make any difference for you for example it's is it the same are there any no more pressuring issues that you would like to see so this is not of your concern at the moment maybe we can ask to the people that are here from my institutions like Monica Sara or Gurell or Katia even if for you having the logo or customized the page it's better for your institution when you are suggesting argos as the dmp2 for having a machine actionable dmp or to use for specific founders data management brand do you have any thought about that I can say that for the time being we are we have a destitutional repository which does not contain data we will have another repository with data but it's yet to come and I think that if you could connect argos to our repository it could be better I mean everything stays in one place you know I think it's a good idea but we still don't have the possibility to test it so everybody is just jumping from one tool to another and I think as soon as we have this new repository for data this would be clearer it also would be easier to make some proposal more than other and to suggest some instruments and tools instead of other this is why I'm just having a look at the different tools I think it's quite friendly as I see because this is the first thing it's it could be you should be attractive and friendly otherwise the researchers won't use it it's just a burden just something they have to do and they don't understand the the reason and also the the possibility that these kind of instruments give them as long as it is too difficult to use if at the end these tools is connected with our repository our system it should be better I don't know what entails because our repository has have is not managed by us directly but we have software managers which are outside for Italy it is Chinneca and I don't know how to to connect it and to it will be also a challenge to to know how they could make disconnections with the tools coming from outside but this is about the data repository right this is I'm talking about now about the publication repository because the data repository is yet to come so we still have to see how maybe this year we will start to implement it but as as to my experience with the publication repository it's not easy to connect different systems especially if you are not the software manager you always have to ask and it depends also on their kind of the settings of the repository the settings of the software platform and they call them customizations you know but I think it is a good idea to to make a connection with a repository as a repository manager I think it's a good idea to have everything within a system so it is also easy for us to to see what is going on and to monitor also how our research is going on instead of looking in the noddle you know the noddle is very good but it's outside if I have to make a report I have to look in different places if I have everything in one place it's easier for us yeah yeah thank you thank you it took some months we can have if you are building a new repository and now ZenoDo has launched a new repository system with the same software of ZenoDo in which you can create your own repository with data that are compatible with open air and it will be very easy for us to connect okay they are the admin venue you mean right yes I can get in the chat okay and being mindful of the time I would like to I don't think that changed I would like to end this communicable with an invitation to this reproducibility cafe workshop that we are organizing together with my colleague Stefania we're working as she mentioned before in the tier 2 project which is all about reproducibility and we have a pilot there where we use Argos to extend the concept of DMPs to reproducibility management plans so so that the plans at the end incorporate more elements on reproducibility we're going to have this to our workshop cafe on the 24th of April 10 to 12 central european time and we would be happy to see there maybe I don't know if we can yeah I think there's a link in in the chat a link to the event with all the details and the registration link thank you thank you Stefania exactly what I wanted to say thanks for adding that in the chat so you can tell me more information there as well as how to register and we're happy to see you also there and if you want to participate yeah I think it's the catholic easter right approaching so I wish you all happy easter with friends and family and I know it's not a long time for you know a long holiday but still it's something and that can keep us you know a bit more you know move away some of the urge of the summer that we all feel suddenly when spring comes so yeah all the best wishes thank you very much to my colleagues as well for being here and supporting this and it was really nice talking to all of you and having this discussion uh I really enjoyed it thank you thank you thank you thank you so much thank you thanks everyone happy easter


Our first speaker this morning is Robert Higgs, who is currently the William E. Simon Professor of Political Economy in the Department of Economics and Business at Lafayette College. That he has graduated with distinction from Johns Hopkins University, is a former professor of economics at my old alma mater at the University of Washington, and I'm going to keep the introduction short in order to maximize Bob's time. Come on, Bob. Thank you, Jim. Consider a fact, an obvious fact, but still a fact. Social conditions are not always normal. From time to time national emergencies occur. They always have, and I imagine they always will. Given that fact, it's of some importance to consider the question, can the Constitution protect private rights during national emergencies? The answer is no. The historical record is quite clear, and in regard to this question, there's no reason to suppose that the future will differ from the past. The outlook, therefore, can only dishearten those who believe that the fundamental purpose of the Constitution is to protect private rights to life, liberty, and property. Founders of the United States established the Constitution, as they said, to secure the blessings of liberty to themselves and their posterity. But time and chance have been unkind to their hopes. They intended their framework of freedom and government to endure through the ages, through storm as well as sunshine. But the dead could not forever bind the living, and the unfolding of our history during the 20th century has brought into being a second Constitution. Besides the normal Constitution, protective of private rights, and we now have a crisis Constitution, hostile to private rights and friendly to the unchecked power of governmental officials. In national emergencies, the crisis Constitution overrides the normal Constitution. The great danger, it seems to me, is that in an age of permanent emergency, which is, after all, the age we live in and the age we are likely to go on living in, the crisis Constitution will simply swallow up the normal Constitution, depriving us at all times of the very rights the original Constitution was created to protect at all times. To present evidence in support of this argument, I provide in the paper a survey, a very brief survey of some of the outstanding events and Supreme Court cases that I think warrant the conclusion I've reached. What I provide is a sample, not a random sample. In fact, it's selected to contain some of the outstanding events and cases. But I would add that it's by no means the whole body of evidence in support of my thesis. There are thousands, I would say, of additional pieces of evidence that might be brought to bear. And some of the sources given in the paper allow you to pursue additional evidence should you wish. I start with the railroad labor troubles of 1916, 1917. In that case, the operating brotherhoods in the railroad industry threatened a nationwide strike. And President Woodrow Wilson, very anxious to prevent such a potentially catastrophic event, induced the Congress of the United States to pass the Adamson Act, the effect of which was simply to impose upon the employers and the employees in the industry a 25% increase in wage rates. The employers challenged the constitutionality of the Adamson Act, and the Supreme Court ruled in the case of Wilson versus knew that the action was constitutional. In that case, the court had to confront whether emergency powers existed. It certainly appeared that the Adamson Act was the exercise of an emergency power. But the court ruled that while the government had no emergency power as such, it did have a reservoir of reserved power upon which it might legitimately draw during emergencies. It was a nice distinction, not one that everyone appreciated, including the dissenters in that case. Shortly thereafter, after the declaration of war, conscription of soldiers was provided for. That too was challenged. Never before had the Supreme Court ruled on the constitutionality of the national draft. And in the draft law cases, the court was unanimous. And in the words of Chief Justice Edward White, the reasoning was that the very conception of a just government and its duty to the citizen includes the reciprocal obligation of the citizen to render military service in case of need, and the right to compel it. During the Great Depression, emergency actions were taken at all levels of government. In particular, during 1932, 1933, 34, 25 states enacted legislation providing for moratoria on mortgage foreclosures. This action was challenged in a case originating in Minnesota, came before the Supreme Court, in the case home building and loan association versus Blaisdell. In a narrow decision, the court upheld the actions of Minnesota. And I might add that in arguing before the court, counsel for the state of Minnesota had been quite open in admitting that the moratorium would normally have been unconstitutional as an impairment of the obligation of contract. But Minnesota argued that these were not normal times, and so Minnesota should not be bound by the usual constitutional restrictions. Majority of the court agreed, as Chief Justice Charles Evans Hughes says, the contract clauses protection of private rights, quote, is not to be read with literal exactness. Also in the Great Depression, federal government abandoned the gold standard, nationalized the monetary gold stock, and abrogated the gold clauses of all contracts, public and private, past and future. This was an extremely consequential act, in various respects. The age of inflation that we've suffered virtually ever since is not unconnected with it. It was, of course, challenged, but the actions of the government were upheld, and again in the words of Hughes, contracts, however expressed, cannot feather the constitutional authority of the Congress. In the war emergency of World War II, the federal government suspended a great variety of private rights, as Clinton Rosseter once said of all the time-honored Anglo-Saxon liberties, the freedom of contract took the worst beating. Again, men were conscripted for war, some 10 million. Japanese Americans, whether U.S. citizens or not, were herded into concentration camps without due process. Plants were allocated by government order, production facilities were seized and operated by the government, many consumer goods were rationed, and extensive price and rent controls were imposed, implemented by the Office of Price Administration. For the most part, the government's actions in depriving citizens of rights during the war were not even challenged, or if they were challenged, they never reached the Supreme Court. The Supreme Court did consider challenges to the price and rent controls, but the court found no reason to deny the government any of the many powers it was exercising at the expense of private rights. In the words of Justice Wiley Rutledge, citizens must surrender or forego exercising rights which in other times could not be impaired. That, I think, is a very clear expression of an emergency powers doctrine. Not everyone has recognized it as such. During the Korean War emergency, the government reinstituted many controls. The wage price controls in particular created a collective bargaining impasse in the steel industry, and again threatened a nationwide strike. President Truman, in order to prevent that strike, ordered the Secretary of Commerce to seize most of the steel mills in the country. The owners of the properties challenged the action, and the Supreme Court ruled on the constitutionality of it in Youngstown's sheet and tube versus Sawyer. The court in that case denied the President the right to seize the industry, and some people read this as a turning point, as an instance in which emergency powers were denied. I think it's a mistake to look at it that way. The case was certainly in no way a triumph of private rights, nor was it a significant check on the exercise of the government's emergency powers. The episode actually involved a power struggle between the President and the Congress. On emergency powers as such, the court actually spoke more in favor than in opposition. The ruling specifically was that the President had no authority to seize the steel mills without specific legislative authorization by the Congress, but no one denied that Congress might well have made such an authorization. In the 1970s, after the Watergate troubles, Congress attempted to recover some of its lost authority and passed the National Emergencies Act in 1976 and the International Emergency Economic Powers Act in 1977. These acts placed new procedural requirements on the exercise of emergency powers by the President, but they did little to detract from the substance of such powers. I don't think a great many people appreciate the extent to which declarations of emergency continue to be made and powers continue to be exercised under these declarations. Under emergency decrees, American citizens recently, and I mean within the last decade, have been forbidden to engage in a variety of travel, commercial, and financial transactions with the citizens or governments of designated countries, including Cuba, Iran, Libya, Syria, South Africa, and Nicaragua. Recent Supreme Court rulings have sustained a wide scope for the exercise of presidential emergency powers. In particular, the legislative veto case, INS versus Chata, effectively demolished the check of a concurrent resolution that had been provided in the National Emergencies Act as a device to allow Congress to overturn the exercise of emergency powers by the President. In 1981, the case of Dames and Moore versus Reagan, the court gave broad construction to the President's power to act under the International Emergency Economic Powers Act, and it went further to say that the President, even when he lacked statutory authority to take emergency action suspending private rights, nonetheless had constitutional authority to, for example, terminate the claims that American citizens had brought against Iran in federal courts. An even more recent case, Reagan versus Walled, 1984, the court allowed an imposition of emergency controls on travel to Cuba without a declaration of national emergency and without even compliance with the procedural requirements of the National Emergencies Act. The outcome of all these recent actions is that during the past decade, American citizens have been forbidden to travel to various countries, to borrow or buy from, lend or sell to the citizens or governments of various countries, to fulfill the terms of valid contracts, to pursue in US courts legal remedies for injuries and takings. In other words, far from having their rights to life, liberty and property upheld by the federal government, Americans have been routinely deprived of such rights under declarations of emergency. In attempting to understand why the crisis constitution has arisen and how it operates, I think it's important to look at what I call three loci of the Constitution. There's been some discussion in the conference previously about the distinction between the constitutional document and the so-called living constitution. Most of what's been said seems to have to do with whether there ought to be a living constitution or not. I'm not concerned with whether there should be, but I make a distinction between three places that you might find the Constitution. One, of course, is the constitutional document, and if you look in that for emergency powers, you won't find them. There's no mention of emergency powers in the document. If the framers intended the government to exercise any different powers or to protect any different rights during national emergencies, they certainly neglected to mention that. Of course, another notion of the Constitution is what Charles Evans Hughes said in a famous statement that the Constitution is what the judges say it is. As I say, constitutional law tells us what the Constitution means. I think that's inevitable. It's not a question of whether you want judges to interpret the Constitution or not. There isn't any choice. The Constitution has always been making law from the very beginning, and I frankly am a little puzzled by people who find that somehow in the 1960s the court suddenly became a lawmaking branch. It seems to me that the court has always been a lawmaking branch. The court has, however, been reluctant to pronounce a clear national emergency doctrine, even in cases like Wilson v. New and Blaisdell. The court took this curious position that there are no emergency powers as such. It's just that there are these reserved powers that may be called into play during national emergencies. It seems to me that in constitutional matters, as in others, actions speak louder than words. A third place that you might look for the Constitution is neither in the document nor in the U.S. Supreme Court reports, but around you. Ever since at least the time of Aristotle, there's been a notion of the Constitution that boils down to the Constitution is how governments act. It's how the polity operates. And I think this is a very important sense of what the Constitution is. I call this the constitutional system. It consists of the conglomerate of beliefs, behaviors, and institutions that actually determine the structure of governmental powers and private rights, and the processes whereby these powers and rights are altered. Clearly, the crisis Constitution is and has for a long time been an integral part of the American constitutional system. If you're going to make bets, you'd better bet that in the next national emergency, the federal government will extend its powers at the expense of private rights to life, liberty, and property. Well, let's think for a little bit about why the crisis Constitution has evolved, why in each episode the government has tended to suppress private rights. In the paper, I go through the same examples I gave a few minutes ago, and I ask in each case, might the outcome have been different? Can we imagine, for example, that the Supreme Court would have ruled differently? Now, of course, we can imagine that in human action, nothing is totally determined. But my argument is that when we consider the political realities and the prevailing crisis conditions in each of these episodes, it's extremely unlikely that the court would have ruled differently than it did. Consider, for example, the Court's ruling on the Adamson Act, 1917. How did the court think about the consequences of ruling one way or another? Suppose the Adamson Act had been struck down. What would have happened? Well, everyone expected that there would be a nationwide railroad strike, and everyone expected that this would have disastrous consequences. The United States in 1917 was extremely dependent on the railroad transportation system. But that was not the end of it, by any means. The United States stood on the brink of war as the court was deciding Wilson v. New. And as Thomas Gregory, who was Attorney General at that time later said, Chief Justice White, quote, knew, as we all knew, that we were on the very verge of war. For the moment, he forgot the facts of the case that was before him. And his prophetic eye was resting on the immediate future, when every proper energy of our country would be called upon to sustain it in its hour of greatest need. Seems to me that the majority simply was not willing to issue a ruling fraught with danger to the military strength of the nation, no matter what the normal constitution might require. In the case of the draft law rulings, the decision was unanimous, but under the prevailing political and social conditions, this was almost inevitable, it seems to me. Those conditions were permeated by war hysteria, superheated patriotism, vigilante attacks on slackers. Men were being thrown into prison even for questioning the constitutionality of the draft. It's difficult to recall just how far Americans went in 1917 and 18, how much they lost, as we might say these days, their cool. One can easily understand why the justice has chosen to transcend the normal constitution and uphold the draft, because without the draft, the government's war effort would have collapsed. Patriots themselves, the justices simply were not willing to pay such a high price to sustain the normal constitution, especially when political elites throughout the land were howling for conscription. Besides, had the court declared the draft unconstitutional, executive branch would probably have ignored the ruling, leaving the court defeated, embarrassed, and diminished in constitutional status. It's been said that it is an axiom of constitutional justice that any decision which the court thinks will not be enforced will probably not be made. I think this was an instance of that. Might the Supreme Court of upheld private property rights in the Minnesota moratorium case? Well, I think that would have been surprising. You must consider the situation. The farm economy was a shambles at the beginning of 1934. There had, of course, been an enormous contraction of real income, and in the farm sector, it had been disproportionately great. Farmers all over the country were going broke, losing their homes, losing their properties. Alternative opportunities were not very good in the event that they lost their farms. Here and there across the country, farm violence had broken out, and specifically in the state of Minnesota, the legislation putting a moratorium on mortgage foreclosures had itself been enacted under very ominous pressures from thousands of farmers gathered in the state capitol, making threatening gestures. To strike down in January 1934, the mortgage moratorium laws already enacted at that time by 22 states would have risk setting off an explosion of farm protest and perhaps widespread violence forced to choose between upholding the normal constitution and averting a potential social and political calamity, the majority decided to avert the calamity. The gold clause cases, I believe, presented the court with what amounted to an executive fed a complete. The government had taken possession of the nation's monetary gold stock. It avoided all contractual gold clauses and thereby prompted a multitude of changes in specific contractual performance. Was the court now to say that the government must return the gold coins and certificates to the millions of citizens who had surrendered them, and that all those who had paid legal tender instead of gold must turn around and pay the gold as initially stipulated in their contracts? Clearly, such a ruling would have led to economic chaos. At least the court believed that it would, and counsel for the government argued that it would. And in addition to that, the disruption of the administration's monetary policy would have been brought about, and that policy was already some two years old. The court was simply unwilling to be a party to the creation of such chaos. During World War II, the Supreme Court's virtual abdication again reflected a fait accompli by the legislative and executive branches. The political branches had created a full-blown command economy, complete with conscription of soldiers, physical allocation of raw materials, confiscation of private facilities, controls of wages, prices and rents, rationing of consumer goods, and a great deal more. Was the court deciding cases in 1944 after such policies had been enforced for years to say that they were unconstitutional? It's inconceivable. And in any event, it would have been futile, and the court knew that very well. The best it could do was to continue to go through the motions of judicial review, biding its time in anticipation of the return of normal conditions when the normal constitution would reassert itself over the crisis constitution and genuine judicial review would again become feasible. Events during World War II demonstrate in its clearest form what I call the logic of the crisis constitution. It works as follows. When elites and masses alike believe that national emergency is upon them, it's not the same as national emergency actually being upon them by the way, it's just that they believe it is. They call on the government to do something. The political branches, acting more or less autonomously, adopt policies. By their very nature, such policies entail costs, virtually all of which fall on non-governmental people. The greater the costs, the more likely is public resistance. That's only a corollary to the economist's law of demand. In the extreme, public resistance jeopardizes the government implementing the policy. Anticipating resistance, governments take steps to conceal or obscure the costs of their policies. And one device invariably adopted is the substitution of command and control measures, which hide costs, for fiscal and market means of resource allocation, which reveal costs. The necessary implication of this substitution is the attenuation or destruction of private rights, rights previously protected by the normal constitution. In some, the crisis constitution, like the normal constitution, rests on a broad ideological base. Public attitudes, values, norms, and expectations condition the structure and processes of governmental powers and private rights in both cases. In the 20th century, the American people have come to expect, tolerate, and in many instances demand that the normal constitution be displaced during national emergencies. Governmental officials understand this public disposition and act accordingly, seeking their own objectives within the altered constraints. Conceivably, the dualism of our fundamental institutions could be unproblematical. That is, we could act according to the crisis constitution during national emergencies and according to the normal constitution at all other times. Some people actually assert that this is what has happened. I deny it. It seems to me that history is not conformed to that pattern at all. In fact, the normal constitution to which we revert after a national emergency is never the same as it was before the crisis. To some degree, aspects of the crisis constitution, as expressed in judicial interpretation and even more so in the constitutional system, are incorporated into the normal constitution. Such legacies mark the aftermath of both World Wars and the Great Depression. There's not time today for me to present an enormous amount of evidence for that claim, but in about three months, my book Crisis and Leviathan will be in your bookstore and I recommend that you all rush out and buy one to find the evidence for my claim. The upshot is that the normal constitution of the post-World War II era has fully validated big government in the sense of an active, powerful, highly arbitrary government far less restrained by the constitutional checks and balances of the old normal constitution, a system that once restrained the interventions, if not the ambitions of governmental officials. Today, I think it's worth saying again, emergency powers as such continue to undergird the government's denial of numerous private rights, especially in relation to international travel, commercial, and financial transactions. Should a genuine national emergency arise, I have no doubt how the government will react. The private rights of Americans, I think, are balanced on a very thin constitutional edge and a wide variety of crises, real or contrived, could easily knock them into oblivion. In conclusion, I ask, can anything be done? And I regret that my answer is not a very optimistic. Effective protection of private rights against future governmental invasion under color of emergency seems to me extremely unlikely. Experience of the past decade, that is the experience since passage of the National Emergencies Act, has shown that procedural safeguards are worthless. They make no difference in effect. Not much more hope can be placed in a reconstituted Supreme Court, that is the appointment of justices favoring a return to the old normal constitution. Even if such judges could be found and appointed, their resistance to the crisis constitution could not have more than temporary effect in a national emergency. Before the fierce winds of adverse political actions and hostile public opinion, even the strongest court sooner or later will bend or break. Ultimately, the preservation of the normal constitution against the inroads of the crisis constitution can be accomplished only if the politically influential elites who make policies and mold the opinions of the masses are willing to resist the passions of national emergency. People must understand that reversion to the status quo ante will not occur, that private rights once surrendered are unlikely ever to be recovered fully. If such understanding and a concomitant commitment to private rights were widespread, we would have little to fear. If the dominant ideology gives strong support to the normal constitution, it will survive no matter what else happens. But if the dominant ideology does not give strong support to the normal constitution, it will eventually be overwhelmed by the crisis constitution. Step by step, a ratcheting loss of private rights will attend each episode of national emergency. And we may as well admit, I think that such emergencies are inevitable. It is to me inconceivable that life would be forever after normal. Unfortunately, elites and masses in the United States today with only a few notable exceptions have neither an appreciation of the ratchet process nor a strong commitment to private rights to life, liberty, and property. And therefore, I must sadly conclude that the most likely prospect is for further expansion of the crisis constitution and a corresponding loss of private rights. Thank you.


Welcome to the man hosted by Kootenai. Ahoy, McCoy!  My name is Gerald. I know, it just seems kind of offensive. It has like a soft G. Just call me Gerald. Just use my name. Gerald, I'm going to read you a quote you once said. He's actually my favorite superhero because he's just as powerful as the other superheroes, but he doesn't have any superpowers. His greatest attribute is that he's highly intelligent. He's just a regular dude who always finds a way to get the job done. Absolutely. And that's probably the nicest thing you've ever said about Ryan Fitzpatrick. I wasn't actually talking about Fitz, but that does sound like Fitz. Who were you talking about? I was talking about the Batman. Are you sure they're not the same guy? You know, usually you see Batman's chin and I think I would know if Fitz was underneath the mask.  Hell, I am with a lot of kids. Do you think you should be doing something cooler like Pokemon or Harry Potter?  Okay, let's start with Captain America. J.J. what? What about Flash? Tyreek here. Excellent. How about Loki? I'm going to say Loki is Aaron Rodgers because he's unapologetically excellent. Spider-Man. Jaylen Ramsey. He can go get any... He lacks confidence. Yeah, I know. He has to take some glasses for that. What about X-Man? Well, that's not one. It's a group. And it's a group of mutants with a lot of in-fighting. Sounds like the Pittsburgh Steelers. I think Aquaman is the coolest guy. Aquaman rides a friggin' seahorse. I love shrimp. I feel like Cam Jordan can be Aquaman. We had wings one time. That is not a fish. It's just a chicken, sir. You have your own Batmobile. I do. What kind of gas mileage does it maybe get?


Hello, and welcome to this presentation of the STM32MP1 DDR memory subsystem. The key features of the DDR subsystem are support multiple DDR standards, DDR3, DDR3L, LPDDR2, and LPDDR3. For all standards, the maximum frequency is 533 MHz, DDR at 1066 Mbps. Note LPDDR3 is supported without on-dye terminal or ODT, similar to LPDDR2 support. 32-bit interface width can be either fully populated, 32-bit, or half populated, 16-bit. Note the device may also be packaged with the 16-bit DDR interface only. Density limited to 1 GB due to the memory map address range. DDRSS is supporting single rank only. DDR3 and DDR3L memories are similar except for the supply voltage. 1.5 volts for DDR3, 1.35 volts for DDR3L. For the sake of simplification, we refer only to DDR3L. DRAM topologies can be point-to-point or P2P applicable with a single SD-RAM device on the board. This is the case with 16-bit DDR3L or 32-bit LPDDR2 or 3-memories, or flyby applicable with two DDR3L devices, 16-bit on the board, and a 32-bit full-populated interface. For the flyby topology, the command address bus or CA bus is sequentially routed to the two DDR3L devices. ByteLanes groups, DQ or DQS, are connected point-to-point. It is also recommended to use termination on the command address bus to VTT. The suitable topology is determined by the SD-RAM memory device and the DDR interface width, resulting in a number of SD-RAM devices considering their density. LPDDR2 or 3 devices are mostly available with 32-bit data bus width, while DDR33 or 3L devices are mostly available with a 16-bit data bus width. The DDR subsystem, or DDRSS, is composed of two main parts, the DDR controller, or DDCTRL, and the DDRPHY, or DDRPHYC. DFI is the standard interface between the DDR controller and the DDRPHY. The DDRCTRL is in charge of convert AXI bus transactions to DRAM transfers at DFI interface. AXI port arbitration, DDRCTRL is equipped with a dual 64-bit AXI. Schedule DRAM commands according to traffic classes, or QoS, for optimal DDR utilization. And schedule DRAM refreshes. The DDRPHY, or DDRPHYC, is in charge of drive command access, or CA bus, and write data, DQ or DQS, according to JEDEC timing. FIFO read data, DQ or DQS, according to JEDEC timing. Programmable initialization of PHY and DRAM for DDR3 and LPDDR2 or 3 standards. This is a simplified block diagram of the DDR subsystem, or DDRSS. DDRCTRL is a multi-standard DDR controller connected to the SOC backbone, and which generates DDR commands at the DFI interface. DFI specification defines a generic interface protocol between a memory controller and PHY interfaces. DDRPHYC is a multi-standard PHY interface, which supports the actual signaling of SD-RAM memory device. DDRPHYC also supports the required initialization sequence, and some fine timing control required by the SD-RAM. DDRCTRL and DDRPHYC have their own control registers. DDRCTRL is connected to the SOC backbone by two AXI ports. DDRPHYC has a slice-based architecture with a command address bus and four byte lanes. The main DDRCTRL features are two 64-bit AMBA4-AXI4 ports interface, or XPI, asynchronous to the controller. 64-bit with DFI 2.1 compliant interface to DDRPHYC. Advanced scheduler and SD-RAM command generator. One-to-one frequency ratio between the DDRC clock and the DDRPHY, a.k.a. SD-R mode. Advanced QoS support with three traffic classes on read and two traffic classes on write. Options to avoid starvation of lower priority traffic. Guaranteed coherency for write-after-read, or WAR, and read-after-write, or RAW, on the AXI ports. Programmable support for burst-length options, four, eight, or sixteen. Write combined to allow multiple write accesses to the same address to be combined into a single write access. Single-rank configuration. Supports the automatic SD-RAM power-down entry and exit caused by a lack of transaction arrival for a programmable time. Supports the automatic clock-stop, or LPDDR2, or three-entry and exit caused by the lack of transaction arrival. And supports the automatic low-power mode operation caused by a lack of transaction arrival for a programmable time via hardware low-power interface. Programmable paging policy can be as any of the following options. Leave page open after accesses. Open page policy. Close page when there are no further accesses available in the controller for that page. Auto pre-charge with each access with an optimization for page close mode, which leaves the page open after a flush for read-write and write-read collision cases. The DDR controller supports the self-refresh entry and exit as follows. Automatic self-refresh entry and exit triggered by a lack of transaction for a programmable time. Self-refresh entry and exit under software control. Support for deep power-down entry and exit under software control, or LPDDR2. Support for explicit SD-RAM mode register updates under software control. And flexible address-mapper logic to enable application-specific mapping of row, column, and bank bit. The DDR controller supports programmable 1T or 2T timing. Refresh control mode can be selected among the following options. Controller-generated auto-refresh is at programmable average intervals. Ability to group up to eight controller-generated refreshes together to be consecutively issued. This reduces the number of page closings, increasing the overall efficiency. When the controller-generated refreshes are grouped, some refreshes can be speculatively issued when the controller is idle for a programmable period of time. Ability to disable controller-generated auto-refreshes. Ability to issue a refresh through direct software request. And user-selectable ability to perform pre-bank refreshes rather than all bank's refreshes for LPDDR2 or 3 devices. This is a simplified view of a DDR interface using source synchronous signaling. The interface has several signal groups. The CA bus group, which consists in command and address signals, they are unidirectional and related to the differential clock signals CK, CK hash. CA signals are center-aligned at PHY output by the Delay Locked Loop Circuit or MDLL. The CA bus uses single-edge SDR for DD3 and dual-edge or DDR for LPDDR2 and 3. The DQ-DQS group per byte lane. These signals are bi-directional according to read and write command. The data group includes data or DQ and data mask or DM signals. They are related to the DQS-DQS hash strobe. For write access, DQ and DQS are center-aligned at PHY output by the MDLLs. For read access, DQ and DQS are edge-aligned at SD RAM edge and the PHY will gate in and out signals and realign DQS and DQS hash for optimal sampling using the SDLL. Furthermore, fine step delay can be applied to individual signals in the group for optimal timing margins. This is covered by the tuning procedure. DDR-PHYC uses a byte lane architecture so that all signals in a group are closely matched. It uses a master DLL or MDLL for command address signals to the SD RAM memory and a master slave DLL or MSDLL for each byte lane group. MDLL helps tune the CK CK hash delay by 180 degrees SDR mode in the case of DDR3L devices and by 90 degrees DDR mode in the case of LP DDR2 and 3 devices. MSDLL is used to delay DQS DQS hash output signals by 90 degrees to center-align write data. MSDLL is used to delay DQS DQS hash input signals by 90 degrees to center-align read data. This is a simplified diagram of the DDR-PHY controller. The physical utility block or PUBL includes the control registers and several state machines. PUBL is in charge of the sequence of the PHY activity, including the DDR initialization sequence. PUBL supports impedance calibration and several built-in tuning with programmable execution. The MDLL and MSDLL are generating clock phases to the internal timing modules or ITMs. This is a summary of the DDR-PHYC features. PHY initialization with DLLs reset and locking. SRAM initialization including MRS and ZQCL commands according to SDRAM standards. Output drive and or OTD impedance calibration or ZCAL. DQS gate training or DQSTRN to position optimal gating of read data. Support read DQ-DQSI centering with fine step delay by software. Support read DQ delay tuning with fine step delay by software. PUBL also supports a BIST engine for at-speed loopback testing. The complete PHY initialization including SDRAM initialization and DQSTRN is shown in this diagram. The sequence is defined and controlled by the PIR register. This sequence is launched after a system reset. Tuning parameters determined by software during the bring-up are saved and restored. The DQS gate is the window during which read DQS propagates to PHY read logic to sample incoming read data. DQS gate position is dependent on the round-trip delay. The DQS gate needs to be positioned to quarter-bit accuracy. PUBL is supporting a built-in DQS gate training sequence or DQSTRN. It is launched by default during initialization. DQSTRN is using the SDRAM array instead of the DDR3 MPR register. By default, row bank column zeros are selected. DQ and DQS can be delayed in fine steps, plus or minus 20 picoseconds. DQ bit delays are used to compensate for DQ bit mismatch, or DQ bit desq. DQS DQS hash delays help optimize the placement for DQ sampling, or DQS read eye-centering. DQS DQS read tuning is a software procedure supported by the STM32 cube MX tool to find optimal settings. Both DQ bit desq and DQS read eye-centering should be done during the board bring up and the determined optimal settings saved to the DDR configuration registers. The power saving scheme is implemented at various locations of the DDR subsystem. SDRAM with pre-charged power down, self-refresh and clock disabling. DDR-PHYC with DDL and IO's low power modes, and DDR-CTL and SOC with clock gating. Self-refresh is the main power saving feature supported by DDR-CTRL. It can be entered in three ways. Explicit control from software or SSR, based on an idle timeout or ASR, or control from hardware or HSR. The DDR-CTRL and DDR-PHYC registers are programmed according to SD-RAM timings and configuration prior to DDR-SS initialization. The DDR-SS configuration is requiring minimal information from the user through the STM32 cube MX DDR panel. The DDR-SS is ready after the DDR-SS initialization. Enabling the AXI port is the final step. Besides the pre-determined configuration parameters, the tuning parameters are determined during the board bring up using the STM32 cube MX tool. Once the DDR memory is configured and the PHY is tuned for optimized timing, the configuration robustness must be tested. A complete test suite is proposed by the STM32 cube MX tool. Configuration parameters are saved and restored before regular DDR operations. For more details, you may refer to the following documents. DDR3 SD-RAM standard, JEDEC, JESD79-3F, LPDDR2 SD-RAM standard, JEDEC, JESD209-2F, LPDDR3 SD-RAM standard, JEDEC, JESD209-3C, RM0436 reference manual, STM32 MP15XXX advanced ARM-based 32-bit MPUs, AN5168 DDR subsystem initialization and configuration, AN5122 DDRPCB design guidelines and STM32 cube MX tool.


describe what a job cost sheet is and how it is used. If we see an essay question like this, we're looking at a job cost sheet and that can give us an indication that we are using a job cost system. So we may first, if we don't know exactly where to start, start off with what a job cost system is, when it might be used. And then we can go into the job cost sheets and how the job cost sheets relate to the job cost system. So a job cost system is typically a system one of two that's going to be used for production processes, although it could also be used for service companies as well. Usually in cases where we're going to have some type of customization, where the things that we're producing the jobs we're working on will be different. And therefore we need to track costs between the inventory or the jobs in a separate way so that we can track those costs that will differ from job to job because those jobs are going to be different in nature. There's going to be some type of customization typically. So we can think of a construction company, or we can think of anything we make that's going to be customized if we have the custom guitars or custom jewelry, anything that's going to be customized could be used, a job cost system could be used in. So within the job cost system, then we have the job sheets. So what is a job sheet? It's going to be the supporting document. It's kind of like a subsidiary ledger. If you take all the sheets together, you can think of them as a supporting documentation, kind of like a subsidiary ledger to the accounts on the trial balance or the balance sheet for inventory, including the inventory that's not yet completed work in process, and the inventory that is completed finished goods. Those two numbers on the balance sheet are just going to be one number for, say, work in process. We're going to have one number representing work in process, and that's going to include a lot of stuff. The work in process account includes direct labor, well, it includes labor, material, and overhead, and it includes those for multiple jobs. And so we need more detail than what it's going to be on the balance sheet or the trial balance. That detail, some of it can be found on the general ledger, as can be found with any kind of account.


Well, thank you all for coming. My name is Morgan, and I'm just representing Neurofidora today. And, yeah, we've got, well, would you like to introduce yourselves? Introduce yourselves, the two of you. Everybody knows me, okay, so I'm Sbyshek. I work on packaging of Neuroscience and science related stuff, and I am creating a festival. My name is Luis Vasan, I am a member of the Neurofidora Seed, I am a packaging maintainer, member of Federal Ambassador, and a lot of other teams, I don't remember the other teams now. And sorry, I'm Morgan Huff, and I'm kind of representing the neuroimaging tools in Neurofidora. And Ankur Sinha, who couldn't be here, is more representing the computational neuroscience tools, and has been, you know, the tour de force in terms of packaging. Anyway, let me, these are Ankur's slides, so bear with me if I'm reading them with you. So, yeah, we started this, certainly more, I was more interested in brain imaging tools, and here we've got a number of examples that we've got tools currently in, not in release, but in queue for, you know, looking at the neuromophology. There's lots of different kinds of neurons that you can model. And here we've got a bunch of different brains, and comparative anatomy is another really interesting area. You know, a lot of the studies that we look at are, you know, probably started with mice or rats, maybe even monkeys. And of course then we try and translate those into human studies. There's a great repository at the Institute Pasteur for, you can get MRI data on all these kinds of animals. Naked mole rats, dolphins. So, as we all probably hear about the thousands of connections between neurons, and these kinds of models that we use, you know, both in computational neuroscience as well as, you know, in machine learning, and kind of reinforcement learning, which we'll talk about a little bit later. And what's going on at these synapses really underlies our best understanding of learning today. So we study a lot of different kind of levels and aspects of neuroscience, the physiology and brain functions, how it's structured in a neuroanatomy, and then how we know that's, at least how the physiology is broken down in terms of pharmacology and biochemistry. And we can hopefully be doing a better job in splitting the tools up and showing you which tools are used for kind of which aspects of this. And now, of course, what we care about are these kind of computational models, both in terms of how the brain's doing something, and of course building up our own computational model on the computer of that process as well. And these all relate to our concepts of the kind of behavioral units in the behavioral analysis and the cognitive analysis. And I myself apply this in psychiatry and it's just one of the diseases. I've also worked on multiple sclerosis, rheumatoid arthritis, different clinical areas that you wouldn't necessarily think have kind of a brain or neuro component to them. But neuroinflammation and neuroimmunology are two really important areas of development these days. The human brain project, and I've brought a few brochures that I brought from Geneva. This is more of the blue brain project, but the human brain project, you'll see some brain-inspired computing. And there's brain scales in University of Manchester and then there's another group in Heidelberg. Neuromorphic computing, something that we don't have any of the tools currently packaged, but that's something where these are all areas that we could use more packages for. And I certainly started in philosophy and consciousness studies are also a very hot area, at least in neuroimaging. We look at locked-in syndrome and people in comas in terms of if they've lost the ability to actually communicate, can you show a brain response to show that there is consciousness and kind of the philosophical and ethical implications of that. At least in the case of Cambridge and Adrian Owen, who's now moved to University of Western Ontario, they are looking to get consent from patients in terms of these people need a rather dangerous surgery. Can they ethically consent to the surgery? So some of the research, well, here's just a general workflow that you probably see in any science lab. And we're talking about Neurophrodor's Day, but we really want to see more cross-pollination between all the different SIGs. And this kind of, we have theory leading into modeling, leading to experimental work, leading to data analysis. And of course in some of these different tools are being used. This is probably better directed graph representation of the relationship between these areas. Okay, so tools of the trade. This is maybe a little more my area in terms of here are the kinds of systems and the kinds of modalities that we collect. So EEG and electrocortograms, those are the intracranial recordings, as well as single and multi neuron recordings that you might do on just slices of tissue or extracted nervous systems.  These days it's going to be multiple time series. The CT and the MRI, those are your more well-known 3D volumetric techniques that are giving you that great representation of neuroanatomy. DOI in this case is diffusion optical imaging. So we can use near infrared light as a means of actually capturing, capturing blood oxygenation. So fMRI, which is the MRI technique for looking at blood oxygenation, can actually be much more cost effectively replaced with just a near infrared sensor and it will shine light right through your skull. So we do have some packages for near infrared imaging. And then MEG is actually another EEG package or modality, just uses much more expensive sensors. PET is the last one there as being a more real nuclear radiation technique where you're going to ingest something that's going to be emitting some high energy particles. But PET is a terrific way of capturing a lot more of the biochemistry and organic chemistry depending on your sophistication and making tracers. So a lot of the neuroreceptor mapping that's been done in humans has been using PET techniques. So of course in data analysis, the data analysis packages that we really want to see more of are going to be the ones that you're probably pretty familiar with in computational Python. A lot of the computational Python packages were actually developed by fMRI researchers. So I don't know if anybody is familiar with Seaborn, but that's a pretty common one for all sorts of disciplines. He was an fMRI researcher at Stanford. He's now moved up to the University of Washington. As well as, you know, our packages and then the kind of statistics behind things like MCMC, so JAGS and STAN and other tools that you'll see for what I would call statistics. And then, you know, what we're going to hopefully talk about a little bit at the end is some of the more traditional machine learning or deep learning tools and making sure those are packaged too, because they're certainly, we see a lot of those being used in medical imaging for both nonlinear registration and segmentation. So it's really improved those areas. So we'll see a lot more dependencies of big packages on those tools. And then simulators. You know, we really, there's a great paper in Nature just recently about the real scientific utility of simulations. And they got a lot of PIs from computational neuroscience labs to contribute to that article. And that's why we were presenting at computational neuroscience in Barcelona this year, where we had a poster. So, yeah, the tools, the other tools, the trades are the ones for, you know, academic writing, blogging, podcasting, video making. Yeah, we see a lot of scientists these days are, you know, their own social media agents, and it contributes a lot to their labs. And yeah, so we're certainly looking to see those tools in. I'd certainly like more tech live support, but and under collaborative tools and utilities. So I think this would be familiar for everyone who's at a Fedora flock conference. Everyone should have freedom to share, study, modify scientific material. And of course, you know, you don't need a PhD to be a scientist. You don't have to publish in, you know, Nature or Science to be a scientist, but you do. You need the tools and you need the scientific method is basically what requirements of being a scientist. And that is really what's behind, you know, us being here at a Fedora conference in terms of this applies to software, which are really tools of the trade here. So free open science implicitly includes relies heavily on free and open software. And here's a particular, you know, we could pull so many, so many great references in the last couple of years. And, you know, I wouldn't want to leave out the open access to journals because, you know, that has been as important as anything else. I don't know how many times where it's like if I'm not connected to my VPN for something where I link, you know, somebody's got an actual journal article talking about open science. And I go to the, I hit a paywall saying, like, please give me $35 to read this article. And sometimes it's, you know, $135. So the, yeah, open access to journals is as important as I'd say the software. And, you know, it's one thing to say, yeah, it's not just the scientific method that you need, but it's also what are the open problems in science today and you get that from reading the literature, you know. So just a little plug there for open access journals. So what can we do at Fedora to help? Well, neuroscience, I mean, certainly one of the things I love about neuroscience and psychiatry is its multidisciplinary nature. You know, we are constantly working with people in different areas. It's really, you know, interdisciplinary teams are the rule pretty much.  But, you know, theoretical mathematicians, you know, certainly physicists and chemists and biochemists and linking in, you know, metabolism, immunology and other areas. And then, you know, understanding where the cognitive scientists or psychologists are dealing with too. And every one of these groups requires another representative, which is, you know, software engineering, really.  That institution is so productive. You know, people coming in, not having to worry about setting up computers, not having to worry about software conflicts and things like that, but just being able to get to work is another mark of, you know, a well-staffed lab. So, too often, you know, we see this in terms of dealing with upstream, you know, what you're really talking to is probably a single developer working alone, or small development teams where they all know each other, you know, access to, you know, particular hardware and resources, although that's, I think that's changing more now with cloud computing. And certainly heterogeneous code quality, let's call it that, and limited use of established best practices, because, you know, again, usually the developers are also the scientists, or more typically, they're the grad students that are developing the algorithms. So, you know, again, these, I think certainly things are better than they have been, but, you know, there's not really an established best practices that they're widely applied. How much testing goes on is another question. And, you know, the other thing being once you want to put things in the door and you want to get other labs using code, are they using that code for the same reasons that that person developed the code? Because they might have tests, but those tests are going to be pretty specific to that particular paper or that particular problem. And, you know, that's what leads to the maintenance and, you know, the interesting project life cycles that you see in terms of, you know, that person's usually working on that code until that paper gets out, and then, you know, their priorities are going to have to change. So, yeah, depending on the lab, you're going to have a lot of different dependency chains, and some of those they get to pick, some of those they don't. And, yeah, documentation obviously is another big hole. So, we've got a lot of projects where we've got, we've got a lot of code that we would like packaged, but a lot of those projects are lacking documentation. So, yeah, the, you know, the community development, I wouldn't say that the know-how is lacking, I'd say that the ability to get people's time is lacking. You know, everybody that I know that has packaged codes to release is super interested in supporting it, but, you know, they just don't have it under their control to give you their time. So, what we want to do, we want to, you know, try and reduce the time wasted, the effort installing, reinstalling, debugging, you know, working out dependency problems, and try and get people more aware of, you know, how these things could be resolved, hopefully in the packaging stage, hopefully in our own testing, and what we bring in terms of having a process in Fedora that we can, yeah. So, making sure that, yeah, the test suites are actually run, and things are reported upstream. And certainly that's something you see where I know I saw someone saying that their software was downloaded 1400 times, but, you know, if it's buggy, then, you know, that doesn't really matter, and how many of those people are going to actually tell the person, well, I, you know, tried to run it, but never could, you know. So, just the downloads aren't necessarily the best metric that people should be using to say, yeah, my code's getting used. No, not really. Anyway, what we're trying to do is be a better liaison between the upstream and users. You know, bring those best practices to a development process in terms of what is our scope as packaging. And certainly we've got potentially better infrastructure for people to look across, you know, across different processors and across particular versions. And what we want to do is really help grow the community and, you know, and mind share. Learning from one another, training as we work, and disseminating information to end users. Okay. So, yeah, so why do we start NERF-Adora? Well, it was really to provide this integrated free software platform for neuroscientists and brain imagers. You know, and I would say, again, like across all the science sigs that we're going to have, we're going to have a lot of shared goals, too. And then really improve the standard to maintain maintenance of these tools, help users develop their own software development skills. This might be the first place that they're going to get some feedback because, you know, it's usually not their advisor's job. And, yeah, and I would say not just make these neuroscience tools accessible to non-specialists, but also to show how non-specialists can really contribute to a scientific software tool chain. So, and obviously to make Fedora the go-to distribution for neuroscience and hopefully for open science. So what we have been doing, so leveraging some community resources to this new domain and taking the community model of free open source to neuroscience research. So less than a year old in its second iteration, but it's really been great seeing it come alive. And we've got 15 active contributors, 10 package managers, package maintainers, five designers, newcomers. There's a core of us with neuroscience backgrounds, both computational and neuroimaging. And I'm certainly super interested to help others learning. I brought a few brochures of projects from neuroscience, computational neuroscience projects. And we've got 105 packages ready to install today, you know, even if you could try those out and make sure that you can't, they do run. You'd already be contributing. There's a whole lot more in the queue. And yeah, we just presented just in July. I was at CNS in Barcelona, which was, it was great. They had a really great day right before the meeting that was mostly covering software packages. And which tells you how important that is to the scientific process that this, you know, almost half the conference was just training people on software tools. So what do we want to do? Make more software available. I know that neuroimaging sides, we've got some big holes in terms of complete pipelines. And obviously improve the documentation. That's, there's a lot missing there. Once you are dealing with the end users and, you know, how much we can do in terms of rolling out some support, but definitely increase the community and convert, you know, a research user base into free and open source software contributors.  And it's not for, you know, it's not that they don't want to contribute, but a lot of them just don't know how, you know, what are the best ways to get their work out there. So, and then of course convert free open source software contributor base into users. And that's something that we'll try and link some of the educational opportunities that are part of human brain project and things like that. To is around getting software engineers involved in scientific projects. So anything is just more for Dora really. Packaging, testing, containers, documentation, evangelism, marketing and design. And here's, here's our mailing lists. We're an IRC telegram, the docs and blog. And of course we're using all the normal Fedora tools for infrastructure. So, there's more science in Fedora than just, than just Nura. So, you know, I would love to learn more from people in astronomy, big data, machine learning, electronic lab sigs, medical and sci-tech. Some of these have, you know, been kind of sleeping for a while. Some of them might not really have any active developers. But I will say just, you know, checking a few key search terms last night. You know, that some really old sig pages come up if I just put in some simple terms. And, you know, I'd love to get those updated. And that, you know, there's a lot of common infrastructure in terms of scientific tools across disciplines that we could be sharing. And these days, the relationship between machine learning and neuroscience is, you know, becoming more and more interesting. And certainly I attend conferences on both, as well as specific conferences that look at the interaction of those. So at Neural PS this year, I know there's going to be AI neuroscience special workshops. Montreal, University of Montreal, McGill do an annual machine learning and AI neuroscience meeting that will be coming in October. And then for medical imaging, there's another great conference that is in China this year. And what you're seeing there in medical imaging and radiology is the overlap of deep learning. You know, deep learning is really taking over a lot of automated radiology and medical imaging projects. So neuroscience is not all about working on core research. You know, like I said, there's a lot of, well, there's a lot of best practices in software engineering that are really overlap with best practices in science, in terms of reproducibility, in terms of testing, in terms of documentation. And, yeah, glad to see that. Open source brain I'm not too familiar with, but, you know, this and human brain project, there are a lot of really accessible sites that I'm happy to point people to, to learn more. Open worm, again, I'm not sure how active this is, but, you know, there's a very simple C. elegans. It's like 128 neurons, I think, or something. Anyway, it's something that should be relatively easy to create a full bottom-up model. They're still working on it, but there's some great projects that relate to that. Here are some, this is something I'm a little more familiar with, although I don't know these particular people. But again, Montreal does an annual, and human brain mapping does annual science art, where people take various things. I thought one of the great, one of really interesting ones was somebody who programmed an MRI scanner so that its beeps and sounds actually played a tune. I thought it was also interesting in terms of making an MRI actually play a song. Different kind of art, but anyway. So, myth too, only researchers can do neuroscience. It's too hard, absolutely not. But it just, it requires, it's that same discipline, you know? And so, if you're familiar with good practices, best practices in software engineering, then, you know, in many ways, you're ready to do science. And so, this particular, he's got a little, yeah, spike time-dependent plasticity example here. You'll see, I guess the blue neuron is representing a perception of food and then another of smell, or is that the smell and then determining curry? Not sure, but what you're seeing there is that this is two neurons that fire together are having some plasticity. And these are getting modeled. Here's just an example of Nest, which is one of the things that we do have packaged currently. Nest is a great package for doing large simulations of a lot of neurons with some sort of connectivity that you've got in Matrix. And I don't think there's a picture with that, but anyway, why don't we thank you so much? Hello, everybody. I'm here just for two or three minutes. My name is Lumir Balhar. I am a Python developer that analyzes and Python maintainer from Redhead. And as Morgan said, a lot of six in Federa was inactive for quite a long time. For example, machine learning was inactive for the whole time it exists, basically. But I'm here to kind of revive it. And I need your help and I think that we are a lot of common machine learning that analyzes and neuroscience has been set. So the main goal of machine learning is to make Federa the best platform for machine learning and artificial intelligence developer. And we really want to do that, but we need something from you. And what we are looking for is we need a lot of information together because I am, that analyzes, I am machine learning developer, but I don't know anybody else who did it except two people on mailing list. Yeah, it's not that much. So if you want to share your experience with machine learning tools, libraries and software on Federa with us, it will be really appreciated. We need to know what doesn't work for you. We can help fix it, package new stuff, etc. What works for you? Also, we need to know some success stories. I mean, if you are using some machine learning that analyzes, etc. tool in Federa for a long time, let us know and we will create some blog post promoting that Federa is a good platform for machine learning and that analyzes. If you miss something in Federa, again, let us know and we will do our best to package it and to make it ready for you. As I said, some success stories and if you create an interesting project, anything related to machine learning and artificial intelligence, let us know, please use mailing list. I'll show you contact me in a while. What we can offer, we can help you with packaging, new software or also package maintenance. If you have a lot of packages you need to take care about and you don't have that much time, let us know. Also, if you are in neuroscience or in science at all, if you have any problem with machine learning, data analysis, etc., etc., let us know, we will do our best to help you solve your problem, always the best if more people take a look or anything else. If you can imagine something we can help you with, we are experienced developer mostly in Python but also in other languages and we know a lot about packaging stuff for Federa, so anything else you can imagine we can help you with. The main contacts are mailing list for machine learning, IRC channel also for machine learning Federa and I was inspired by Telegram group for Neuro Federa, so Telegram is coming soon in summer as well. Maybe also we will bridge from our city to Telegram. But yeah, feel free to use anything to contact me. We just created a sick group, sorry, fast group, so now we are able to commentate packages in the right way. We are almost ready but thank you very much that I can use a part of your talk for this because I am really new in machine learning sick and as I said I am trying to revive it so I missed the CFP deadline for a vlog so I cannot do my own talk, so I use this two minutes free at all. Thank you very much. Thank you and yeah, I wanted to mention with just, well, did anybody have any questions that didn't get addressed? Yeah, please. I guess one of the major pitfalls that the project has right now. Good, well at least in my opinion in the neuroimaging we are missing some real staple packages. If I was going to do a course which we have done previously as part of human brain mapping there are a couple of pipelines that are going to be the go-tos in terms of I have done an fMRI study. This is how everybody else does it. And what is really great at least in fMRI is that there is lots of open data. So I wanted to, somewhat related to this, I just wanted to push open neuro as a great resource in terms of, you can download and play with real human fMRI data today and they will give you some of the resources. Well, anybody else want to speak to what are some of the limitations or holes in that? Yeah, I think I have the same feeling that if you try to do some real signs that you will find that well, 100 packages are there but I don't know, we talked about phoenix missing, we talked about the other context, there is a cytoscape thing for doing graph plotting and many, many other stuff that is missing. And I think that the number of scientific users of Fedora is not high enough to attain good feedback loop where people complain when stuff is broken and as a result there is stuff missing and the quality sometimes of the stuff in this package is not high enough. And if we make it possible to use Fedora as a providing for experience, I think that this will improve and then there will be a positive feedback loop. That's something that I've certainly experienced is that meeting a lot of people who are using Fedora but they haven't been contributing back, they just didn't know that there was a group that they could potentially be getting some of their contributions passed on. But also in talking, it was great to see Igor's talk about cross distro collaborations. Sometimes we could be working more with neurodebian in terms of if we've got some issues with upstream choices, we could be working quite well with them in terms of getting more people, showing that there's more people that would be interested in getting those changes. So yeah, there's a lot of great, there's a lot of opportunities for getting involved and helping. But yeah, whether we've got complete pipelines for our core focus is questionable. One good thing that is happening is that Python 3 supporting Fedora is really good and Python is the language of science. So if you want to develop software for scientific purposes, then it makes a lot of sense to switch to Fedora and I think we should be able to take advantage of that. Just a comment. Yeah, I wanted to say that there are many, many fields in neuroscience that people talk about, like people analyzing modern behavior and there are so many packages. So also probably reaching out to scientists and asking them what kind of software they're using, what kind of software they would like to have in the distribution, what would make them change their operating system to do something else. Exactly, this is the same for machine learning. I wanted to also just make a quick pitch or at least tell people about BrainHack. So we're kind of focused on packaging and getting things into Fedora, but if you want to learn more and have a community where other people are doing kind of citizen science, BrainHack is a great resource at least for the neuroimaging. They can point you to the open data repositories that exist. In computational neuroscience, its strength is that you're usually doing simulations. So we can generate data, I mean generating data is what we're trying to do with these tools. And I'm not sure some of those, if there's an equivalent to BrainHack for those. In terms of the people building their own EEG equipment at least, Neurotech X is another great site, another great organization. They've got chapters worldwide based in Montreal, but chapters all over. And EEG equipment and at least cheap transcranial direct current stimulation equipment is very easy to build. And there's a lot of good resources for people working on their own. Anything else you want to cover? Yeah, I think one of the problems that we are currently facing is mostly upstream dependency. So on single, leasingly-mated projects only, we're not doing that first. That is the biggest challenge we are facing right now. A lot of good software is pending for packaging due to upstream. As well as a lot of stuff is packaged but not documented. And it's hard to test when you're... Any other questions? I see a hackathon slide. Yeah. I saw that same slide. When is the hackathon? The plan is to package stuff, basically to work on issues, impact software and package more stuff and to have a quick turnaround where you can submit a package and get a review and submit it to body and get five plus ones within five minutes. And then to be... But if people want to get involved and you're not sure where your talent is, 10 a.m. We will also be working at 10 p.m. No, no, no. Please, please join us. And the other thing is, you know, please come talk to me if you're not sure how your skills can be best used. Like there's always, you know, depending on what you're familiar with already, if you want to put those skills to use, I'm telling you there are opportunities. If there's new things that you want to learn. I'd be very happy to point you to... Usually, if you don't have a telegram group, make the list for the product, if you have the role of package, come, if you don't have the role, come. You work with your first package, the product, you're building a sponsor, a package sponsor, and a package sponsor. Yeah, a lot of people in this conference are special package managers. And hey, let's go out and help to the neuroscience. Yeah, yeah. Alright. Thank you so much. Go to the bar. Thank you.