Bestand wählen
Merken

Edacore: Less work for everybody

Zitierlink des Filmsegments
Embed Code

Automatisierte Medienanalyse

Beta
Erkannte Entitäten
Sprachtranskript
right below all by saying the into about an hour for which hopefully means less work for everybody so an introduction about who I am something about the idea of this what the scope of the projects is that's very open what I imagine are some
deliverables for the 1st version the concept of parameterization which I think is an important part of of this project a bit about Developer Resources of my plans for the future and perhaps others and impact so my name is kept as the new year I started taking things apart when I was 4 and a little bit later I managed to put some things back together and a little bit later killed Phil I've managed to build something mild and I've
kept going errors since because a lot of fun I I do software as well as hardware and on on many different levels I I have lots of register programming experience on machines from 8 to 64 bits uh I've also done went back and things and I make use of these enzymatic every now and then but nothing too fancy but uh but what what's needed you might have seen some of you might have seen me in around the core approach project live use the um osmocom of sauce cheese and things live SSH true or perhaps she program of lesser number still interesting project of mention that at the end if we have time so the inner core idea is is really simple and I think anyone who is or has done something in this domain has already had it that the point is we have a lot of duplicated information a lot of duplicated uh data where we don't really need to in in lots of different tools uh well in lots of different in in different tool suites to start with but even within a single tool suites uh we have perhaps different data formats for things that could actually be sharing a single data form the I want to make a part library that can do anything that the open-source tools need the and also ideally uh servers the industry so anything perhaps before and after world mostly after the design tools I think that the inner core data should be usable also by the VADs so I'll get back to that in a bit the particular feature of open source is really reuse so we need to do this and I also I mean at so that show hands how many people have created of footprint based on the data sheet how many of you thought that that was a bad idea and that you should actually be it should be necessary to do this yes OK so let's let's fix that and and I would like to have the vendors input their information because they are producing these datasheets anyway right so they have this information structured somewhere and I want to put this into it of and and use it and and stop making these footprints of well this ties into so but sometimes you don't want to use exactly what they recommend and this ties into the parameterization of the effective already now the so this is the 1st time I ever publicly mention this project and it's it's it's as it says on the bottom this is completely vapor where at the moment but but that of the the uh still there is 1 major component vendor who said that they are willing to convert their internal data so that's awesome and I also got an e-mail the day before yesterday from the tool vendors here and and you want to talk to me and they use this so many health work on it I don't know I I hope we can have a chance to talk still later a benefit of it I core as I see it is also that it's going to be more up-to-date it is more up-to-date you can do online updates and I suppose that the commercial tools do that as well but the open-source ones uh don't yet so much and bursting of the libraries also I think important feature to keep track of what you have in your design what you want to use and how can so but the ABS vaporware uh so far let's see a question that that we have to think about is what is the scope of this going to be and my quite ambitious goal is really to go from from right from the beginning to all the
way to the finished product that baby steps right so uh I think the 1st step is is somewhere schematic PCB boundary or perhaps going into both of them a little bit so something like symbols and and perhaps that lists as well but if we're doing that lists then as we heard before or as we know them this is also important for simulations of them with some they have to be considered 1 more set of requirements or or specifications needs the so far there all flat text which is good in a fight text in the open-source tools this is good very large seemed to be popular for the next list so maybe that will simply solve itself and the core want need to deal with netlists and then that will all be very large it seems to be going that direction footprints on each shared uh on common and then there's the what I call parts so that's the so far my my highest level constant in uh for the data model so grouping symbols and footprint and lots of other things also 3 D models for apart and so what is it and and parameterized parts so different kinds of packages for of a particular part perhaps is needed if you have a in the in the schematic you want to say I'm using this circuit this this see but at that point you don't care what packages the board layout you still this needs to be in the same it is the same circuit so for simulation you don't want to have 2 different ones you want to still have just 1 and the vendor will also probably only have 1 model for this and so yes and you to keep this in mind and for report files and Gerber files and and as it says on the game there's going to foundries and so on uh there's a lot of geometry to to
consider and and yes this is also also still still open uh so what exactly so how much to try to do how much can be done by a single their model the what I think should be in 1 4 and 0 is the well at the start of a data model so abstracting performance that are there so far and some kind of database
implementation for this model uh by envisioned a C library for accessing the data so this is what the application developers can use you use that to to work with this data a nicely version and an easy to use and with a permissive license so that it can be use really everywhere without any problems and use it I get it out there have when application I think is important for crowd-sourcing data so that people on the web and at home and that the things in but we want to know if they did that so that I keep track of what I've done and I know that that's good or bad parametrization so there are a few use cases where I at that I've come across where i'd like this uh to be possible so maybe I want to just some real sizes across the whole board that's easy to do and you not so easy perhaps lessons in like that I don't know I haven't tried it uh more difficult is the 2nd 1 I want to hand sort of this board so please extend all the pads outward the packages uh so that I have a bit more space to work with but this is only applying to the footprint and I don't want to make a whole copies of the footprint and mess around with adding the 2 of them it's it should be all associated to this 1 part the and simulation and other use cases will add were more requirements uh um but also more possibilities by developers the was said before there are a few engineers who do both new electrical-engineering and computer science it's more more locked in to the industry the knowledge I a I think is so I've heard from several academics here please put your students to do cross-discipline things I I think this is hugely important I also know that we have some great developers in this room and we've already heard about 2 instances of sort of overlapping work with the next lists in in quarks and and bias and GDA there are other netlists that seems to be converging where a lot which is great there are uh borders files and this footprints which are at the moment different in like that and you go and I propose to let's do these things just once and to the right and of them together the in so I the project exists only with the name uh I have a bunch of maintenance and I setting up a track in a gift they're starting to write about uh until that's done please come to 3 node and if nobody else is is going to help them and I will slowly start to do this for footprints and try to use would the core In both PCBs and PCB new so I'd I'd love to b with weighing about uh the footprint but the footprint data model is in the can and and learn about that when we're the and that's what I what I have to say so thanks for for listening and thanks to the volunteers and and or in doing this b and you need to be the sake and that the then let's talk about this will this like the the the yes by phase so yes I think metadata such as licensing right the question is will the data model include licensing information and and the answer is is yes I think that is a very important thing to include no you are al also ask about models so this work is that we want to know that was all all you have more the money and the the right so you can for what you you all the time right yes so yes so that all those of you who are you want this produce and you know what it was all the war was going on here so you want to be with the with the sum of the of the of the use of time yeah so this is the only thing you so something to comment about licensing how the many proprietary libraries contain models and symbols which are difficult to reuse and a set of Comanche about uh many symbols and footprints which are licensed under GPL with an exception for commercial use or any news site like me I just like the CCA can compile come proprietor programs the question on you still have
the model which I want show to directly in the world so we hear this all this was all the more so that is what we call on all the the theory of mind and you wouldn't have which is shown on all of the of the of the the question that we know all this all the all the so all the all the all over the world knowledge in the area so you you might not want more Europe all over the world it it is a very and is the are but the thing in the the so we the look the so a comment is that many crowdsourced footprints uh many many people are worried about the quality of crowdsourced footprints and yes uh and and I'm worried about the quality of my own footprints even but but it is a key key thing to get the vendors involved in this and and have them provide their footprints and it seems like they might want to get how do we get it back by the end of the week and I will not you the the we have the that the in the that's a that's a great great point and a good good input to consider that there are sometimes very specific requirements on footprint standards or symbol standards for that matter which uh need to at least be documented in the metadata so the tools can can find them and to decide whether and the user can decide whether this isn't a usable piece of data or or not do you know the sign you sign it was 1 of the final I think of I think some kind of authentication of the source of those so the question is about about signing vendor data vendors would be able to sign a date and I think that's important I think it's yes there some kind of certification or or yes make sense but what have all that you get is of the same thing in to the schools you can be the right thing he said the same thing that that's what that is book that so the question about how to deal with many different versions of the essentially the same footprint for example or symbol the the important thing as so and and the common that the user interface problems yes the important thing is that these are all these should all at the very least belonging to the particular asserted that that particular chip that they are for the let's start there because at the moment they don't at the moment it's just a flat namespace of of lots of different parts and and the baby steps and associating different footprints with 1 particular part so that at least the symbol stays the same or there are 2 variations of the symbol and for variations of the footprint and I can choose which combinations I I like but it's still the same logical part this is something I'm looking for time for 1 more but the law and so the point is and that the I think that's a really good idea so there are some common that there's uh previous work and ISO standards and we certainly let's let's let's see what they've done and if it makes sense and if it's enough possibly it isn't really enough for what we want to do or it's too complicated for what we want to do then maybe we don't do that in version 1 or maybe we have b and if
Entwurfsautomation
Projektive Ebene
Programmbibliothek
Bit
Punkt
Mereologie
Versionsverwaltung
Übergang
Eins
Minimum
E-Mail
Suite <Programmpaket>
Softwareentwickler
Hardware
Ein-Ausgabe
Sinusfunktion
Software
Entwurfsautomation
Diskrete-Elemente-Methode
Rechter Winkel
Server
Dateiformat
Projektive Ebene
Information
Disassembler
Programmbibliothek
Prototyping
Subtraktion
Automatische Handlungsplanung
Zahlenbereich
Virtuelle Maschine
Systemprogrammierung
Physikalisches System
Open Source
Domain-Name
Weg <Topologie>
Software
Programmbibliothek
Zusammenhängender Graph
Biprodukt
Optimierung
Ideal <Mathematik>
Hardware
Meta-Tag
Open Source
sinc-Funktion
Einfache Genauigkeit
Telekommunikation
Mereologie
Parametersystem
Speicherabzug
Innerer Punkt
Subtraktion
Bit
Krümmung
Mereologie
Punkt
Gruppenkeim
Räumliche Anordnung
Whiteboard
Eins
Richtung
Informationsmodellierung
Spieltheorie
Diskrete Simulation
Gammafunktion
Umwandlungsenthalpie
Open Source
Datenmodell
Spieltheorie
Mailing-Liste
Symboltabelle
Elektronische Publikation
Biprodukt
Konstante
Randwert
Diskrete-Elemente-Methode
Whiteboard
Menge
Digitaltechnik
Mereologie
Simulation
Speicherabzug
Programmbibliothek
Simulation
Verkehrsinformation
Bit
Gewichtete Summe
Mereologie
Krümmung
Compiler
t-Test
Versionsverwaltung
NP-hartes Problem
Kartesische Koordinaten
Raum-Zeit
Metadaten
Kommandosprache
t-Test
Phasenumwandlung
Softwareentwickler
Datenhaltung
Güte der Anpassung
Spieltheorie
Ausnahmebehandlung
Softwarewartung
Entwurfsautomation
Diskrete-Elemente-Methode
Menge
Rechter Winkel
Projektive Ebene
Information
Programmbibliothek
Simulation
Parametrische Erregung
Instantiierung
Web Site
Metadaten
Implementierung
Whiteboard
Datenhaltung
Knotenmenge
Informationsmodellierung
Weg <Topologie>
Benutzerbeteiligung
Programmbibliothek
Softwareentwickler
Optimierung
Ereignishorizont
Informatik
Implementierung
Graphiktablett
Datenmodell
Datenmodell
Mailing-Liste
Quarkmodell
Symboltabelle
Elektronische Publikation
Quick-Sort
Whiteboard
Mereologie
Simulation
Speicherabzug
TVD-Verfahren
Subtraktion
Mereologie
Punkt
Momentenproblem
Schaltnetz
Versionsverwaltung
Physikalische Theorie
Metadaten
Informationsmodellierung
Vorzeichen <Mathematik>
Ereignishorizont
Umwandlungsenthalpie
Softwareentwickler
Namensraum
Benutzeroberfläche
Digitales Zertifikat
Benutzerfreundlichkeit
Krümmung
Symboltabelle
Quellcode
Ein-Ausgabe
Entwurfsautomation
Flächeninhalt
Fehlererkennungscode
Parametersystem
Mereologie
Authentifikation
Programmbibliothek
Standardabweichung

Metadaten

Formale Metadaten

Titel Edacore: Less work for everybody
Untertitel Crowdsourced parameterized parts library
Alternativer Titel Electronic Design Automation - Edacore
Serientitel FOSDEM 2015
Autor Stuge, Peter
Lizenz CC-Namensnennung 2.0 Belgien:
Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen.
DOI 10.5446/34359
Herausgeber FOSDEM VZW
Erscheinungsjahr 2016
Sprache Englisch
Produktionsjahr 2015

Inhaltliche Metadaten

Fachgebiet Informatik

Ähnliche Filme

Loading...
Feedback