Josh Moore: I think we're good. Okay, I'll share my screen for just a second. I want to make sure everyone knows how are using the hacking D document.
Josh Moore: Um,
Josh Moore: So the links in the chat. I'm at the bottom of the file. You can see all the notes from the previous conversation. So the European and Asian conversation, plus a couple of crazy East Coasters um they get lots of credit
Josh Moore: So we'll be filling out this session. I've left the topics that were discussed in the morning. So if anyone wants to recap, we can go. We can talk about those. Put your name beside them and then we'll start to order the topics by by interest. So the more
Josh Moore: The more names that are besides something then
Josh Moore: The mortal bubble to the top. If you have questions, and then you want to talk about anything you want to share, by all means, um,
Josh Moore: Alright, so that's probably enough for me. Before we dive into things so
Josh Moore: who showed up. Alright, so go around the room, my participants list will do the non dundonians first alphabetically, you can start to prepare yourself.
Josh Moore: Is mark at the top of the list. I assume that all change. So I think Bill you're at the top, you want to take about a minute to introduce yourself. Someone yeah said has a clock. He will let you know when you're running over but this went pretty quickly. Last time, so go for
Bill Katz: Me. Yes. Yeah. So, I'm Bill cats. I'm with Jeanette Leah, the fly em team I designed David and I'm working pretty extensively on data stores matches to image.
Bill Katz: Formats or segmentation. But basically, a little bit more general. In terms of data types. But the key thing. I'm also very interested in is branch burgeoning in creating a GitHub like way of starting to do data sharing among you know various image formats, etc.
Josh Moore: That arena.
Bill Katz: That's it. Thanks.
Caterina Strambio: Hello, Katrina stranded Castilleja I am here.
Caterina Strambio: Primarily, to make sure that we are, I'm working primarily on the metadata side microscopy meta data.
Caterina Strambio: To extend the Omi model.
Caterina Strambio: And I'm here, primarily to make sure that what we're doing, you know, it matches what you guys. I mean, what the the data container will will have because obviously the two things are very connected that is going to be as a different community call about the metadata aspects.
Caterina Strambio: Thank you.
Josh Moore: I'm here.
Damir Sudar: I'm
Damir Sudar: Working for a small company called Quantitative imaging systems and closely associated with Oregon Health and Science University important
Damir Sudar: My interest. This primarily it's very similar to cover pettiness, because we're on the working group trying to come up with that metadata standards called set. And I'm also very interested in the data container site because a lot of our data is in
Damir Sudar: Formats right now that are difficult to handle. And so a new the new way of storing pixel data is desperately needed lovely part of that.
Thanks.
Josh Moore: David
David Pinto: Hi, I'm David from micro University of Oxford. I've been here this morning. A similar to discussions going to be a good evening and
David Pinto: I've mostly worker at the moment in acquisition software for microscopes. So I'm interested. How can you know use these not only to save data.
David Pinto: In, you know, recognize you for much, and as well, like the meta data since our focuses is, you know, quite exotic microscopes and these devices. So unless you can make use of these tools.
Josh Moore: Davis.
Davis Bennett: Hey, spin it, I'm engineering a research campus and I work with a project team that is
Davis Bennett: Really big fix them data sets and generating tons of extra derived volumes from those and then moving them around three and making them all shareable
Davis Bennett: So I have strong opinions about multi scale metadata.
Davis Bennett: And, you know, all kinds of image container issues, kind of like sheet microscopy. So my data has no time access now, but I'm axis.
Josh Moore: Here in
Eric Perlman: America work. Previously on in a softball with TM and various large volumes of data. So I care about multi scale for people to access it, and most recently have been working with
Eric Perlman: Jackson Lab on us arranging slides.
Eric Perlman: And yes, I am here for the second session but I figured out, mostly sit silent unfortunately couldn't hide from Josh
Josh Moore: More Eric's yeah
Eric Wait: My name is Eric. Wait, I'm at the advanced imaging center edge anemia and my interest is getting
Eric Wait: Our visitors come in and use our scopes and it's kind of a one off for them. So how can we make data that they can use them at their Institute and maybe make something more cohesive for for people to use
Eric Wait: With us with the event scopes and maybe with their scopes back in their, their home Institute.
Josh Moore: Eric
Erick Ratamero: That's me, I guess.
Erick Ratamero: Yeah, my name is Eric Romero. I work at the Jackson Laboratory, together with the other Eric THAT JUST TALK LIKE TO TIME TO TWO PEOPLE GO.
Erick Ratamero: I've been doing this by image analysis thing for the last three years or so, first in a facility contacts. Now in it kind of contexts.
Erick Ratamero: And jack seems to be like a place with a very specific intersection of people with the capability.
Erick Ratamero: The expertise and the interest and the bandwidth to actually work on questions like, what do we do in terms of file formats for the next generation. So we are interested and trying to take part on this this journey to what comes next.
Erin Diel: Hi everyone, I'm Aaron deal. I'm an application specialist with Glencoe software. So just really interested to hear how everyone's been using the tools and learn about
Erin Diel: What you want from them.
Josh Moore: Never ready for how fast Aaron is so even
Ilan Gold: Hi, my name is Ilan I work with Trevor, who I think will do some stuff later based on the order we're going in the work on this bizarre and basically bringing
Ilan Gold: Your data to the to the web.
Ilan Gold: And sort of its primary forms will use web beyond sort of similar theme to the party to give me like fast editing. So I guess my interest right now is mainly in making sure that you know things are ready for for viewing in the browser.
Jamie
Jamie Sherman: I worked at the Institute for Social Science kind of an engineer scientist role and basically my focus is on
Jamie Sherman: Trying to eliminate barriers for us being able to share our data in a more open format in more open formats and click just getting it out of the proprietary formats that we're dealing with. And
Jamie Sherman: Ideally, like we've been using quilt predominantly for sharing our data, but my major interest in the next gen formats is that it might actually allow us to put our data in the cloud and not have people have to download things because that just really doesn't work so well.
Jamie Sherman: Anyway, thanks.
John
John Bogovic: My name is john book I'm part of this off of leverage and helium. I'm a contributor to image a in Fiji and I've been one of the bigger contributors to end five which is one of the newer block based file formats.
John Bogovic: In this context, I'm mostly interested in, I think, as many tools as possible, be able to open the file formats or file formats that we come across come upon
John Bogovic: Since it's frustrating to see people on the user end having to consistently and
John Bogovic: Almost always receive data from one format to another in order to push it into different tools. So while I don't expect there will be one file format to rule them all.
John Bogovic: Whatever we come up with, I would hope it would be easy for developers to write inputs and outputs right readers and writers for that's one of my invested vested interests. So that's all
Thanks.
Mark
Mark Kittisopikul: Me I'm Marcus awful and currently as associate that a system engineer.
Mark Kittisopikul: I'm mainly attached to the collab with moment. Um, so I kind of inherited the legacy of color. Walk format.
Mark Kittisopikul: And currently fairly interested in how to receive
Mark Kittisopikul: Store away data for legend across the
Next,
Nicholas Sofroniew: Next Friday. If I'm reading the emerging tech team, the chance, like a bag initiative, we're focused on trying to provide or improve access to reproducible quantitative by image analysis. I'm also on the steering Council.
Nicholas Sofroniew: And Nicole contribute to the party project a multi dimensional image view of a Python and that we have a plugin infrastructure to support reading and writing files and I'd want to make sure that
Nicholas Sofroniew: Any file format that you know were able to easily read and write both pixels and metadata, I think, you know, going beyond that. I'm probably also interested in representations that are
Nicholas Sofroniew: Conducive to saving process data to not just roll pixels as well so you know segmentation masks. Even things you know that end up being much smaller in size but still need to be standardized around metadata, you know, shapes polygons, etc, etc. So that's just me.
Nicolas Chiaruttini: Hello everybody. So my name is Nicole me I'm a microscope East and I perform also image analysis for users. You know microscopy facility at EPA fell in Switzerland.
Nicolas Chiaruttini: And as such, we are using a lot of Fiji and you met Jay and so I'm on the Java side and our main issue is to be able to give to users.
Nicolas Chiaruttini: unified way to open the data because we have microscope four monitors Nikon HR everybody all the stuff, and we hope that one day they will come up with a fight for much, which is good.
Nicolas Chiaruttini: Which has a lot of meta data and, in particular, I'm interested into position on meta data. So when you combine different schools.
Nicolas Chiaruttini: A bit like in correlative em, but also in microscope, you know, you have very big over of us, and then your sport or detail in some parts why I'm here. I'm really interested into combining also also in three dimensional space with different resolution. So that's my main focus. Cheers. Susanna
Susanne Kunis: That's me. Hello, I'm Susanna coolness from us network from the university and also my book and
Susanne Kunis: My focus is more meta data and capturing of meta data from Microsoft data and linked the data, but we working also on how we can share data and the base presentation that we in different facilities and so I'm happy to observe this discussion, how we can make this change. Thank you.
Trevor Manz (he/him/his): Everyone I'm Trevor has been mentioned I were mostly a consumer of a lot of the hard work from the only community on these next generation file formats and trying to make sure that
Trevor Manz (he/him/his): These cloud friendly format we can access in the in the web browser as well so
Trevor Manz (he/him/his): I've been working on this project, which is sort of the web based viewer for these types of pixel data and then also GA S which is a JavaScript implementation star, which sort of factories intelligent things and also next generation software.
Josh Moore: There we go.
Ulrike Boehm: Sorry. Hello everyone.
Ulrike Boehm: Again, I'm unfortunately right now in the lab. No, not unfortunately actually quite good that I can be in a lab. But anyway, so my name is already kaboom. I'm working at the advanced imaging center at omnia currently I'm with
Ulrike Boehm: The multi focal instrument, but anyway. So at the beginning of the year, I was actually participating
Ulrike Boehm: In a conference called software for microscopy was, which was mainly focused on acquisition acquisition software.
Ulrike Boehm: But one of the major parts was there. Also the discussion about good data formats and as I can still recall from the discussion.
Ulrike Boehm: People were already kind of envisioning the next type of data format and people were arguing about which data format is a good one. But what I think currently what we might need are
Ulrike Boehm: Really, how can I say standards, also for the people who develop upcoming data formats to make sure that they actually fit into what's currently
Ulrike Boehm: The norm, because I think Jason can maybe say they're a little bit more about but for example buyer formats. I think they adjust the they are software currently such that lots of data formats can be used. But every time when a new data form, it comes to the
Ulrike Boehm: Data from. It comes to the market. This has to be changed again. And I think this is a hassle for lots of people in a thing. If I think we, if we have a standard and place it might be also easier to to integrate all of these and to make the life for everyone kind of a bit
Ulrike Boehm: Easy. I just only briefly have to look at my notes if I forgot something. I am mainly because also
Josh Moore: Just have more time.
Ulrike Boehm: Okay. One thing was also very important. I mean, currently I'm also part of the corporate initiative, which is currently focused mainly on capturing standards for microscopes mainly hardware standards to guarantee that
Ulrike Boehm: Everything is nicely in line. But to my mind hardware standards shouldn't be the only stuff. That's right. I think it would be actually be great if even
Ulrike Boehm: This community here when we talk about data formats can be also kind of linked to also the other initiatives which were already kind of currently going on because I think right now there's lots of momentum in the community.
Ulrike Boehm: And we really should kind of try to really get as make sure that as many voices as possible are being heard.
Ulrike Boehm: And yeah.
Josh Moore: I think we all agree with you. So actually, we should probably just take that recording and, you know, send that around to people, that's exactly what we all want to say were completely behind you.
Josh Moore: Um, and maybe we can get a topic listed. If you know if there's more we can do about making that happen. We'll get back to it but just we had a couple of people who showed up. So getting through. It was Blair showed up and then Allah
Blair Rossetti (Janelia): Hello, my name is players, Eddie. I work with Baraka, and with their weight at the AC and happy to see many familiar faces and hear what's going on.
Ola Tarkowska: I am a lot. I work in sanker
So my interest is basically in microscopy platform and coming
Josh Moore: Cool, so will rush through the Dundee team. Plus, Melissa, Jason, you want to kick it off.
Jason Swedlow: Sure. Hi everybody I'm receive any of you. Again, my name is Jason. Hello, I'm at the University of Dundee work with the army team. My role there is more or less to keep the money rolling in, and
Jason Swedlow: Try to Yeah keep everything on track.
Josh Moore: Do you go
David Gault: Hi everybody. So I'm David Goltz have a developer on your meeting primarily working on bio formats and all native
Petr Walczysko: Hi, my name is Peter I DO WITH YOU. ME TO mainly the outreach is and quality assurance.
Sebastien Besson: And Sebastian, I'm working for with me to be mostly interested in the all everything from at related from by former to imitative and, more recently, heavily involved in the image data resource.
Simon Li: I am certainly one of the mirror developers and also one of the main idea, our developers and sis admins. So I've seen it was so poor data that's coming into the idea that hopefully benefit from the performance discussion we're having now.
Will Moore: I am will I'm mostly work on the web viewing side of a mirror.
Will Moore: More recently just starting to look at how to show me the data and the clients in the web and in an apartment.
Melissa Linkert: And I'm awesome. I worked at Bank of software and collaborate with Ami team and I work on pretty much anything you can think of that relates to file formats.
Josh Moore: Cool, thank you everyone. So we're 28 people and we got done in 23 minutes. So on average, big golden stars. Um, so how do we want to proceed. So the
Josh Moore: Working backwards. There's there. There are no new topics.
Josh Moore: And there's a few people who have added interests. So this might be a good time for everyone to take a second and think about what they'd like to talk about, um,
Josh Moore: I have my list of what everyone mentioned, so I'll probably bring those up, if no one else says anything
Josh Moore: Um, and then I suggest we let everyone get a chance to ask questions about the couple of videos that were posted. So how many people actually watch the videos.
Josh Moore: Oh, that's actually much better than the morning crew so you guys had more time. Awesome. So I'll assume there are a couple of questions on the videos.
Josh Moore: And we'll get to that in just a second. But first, before anything else happens to anyone. Is anyone lost or has anything been mentioned that no one has an idea about what it is that we need to cover
Josh Moore: Someone actually didn't need a favor this morning of asking what is in GFS and so we could actually start off with that. So it's, um,
Josh Moore: Who unmuted.
Josh Moore: Okay, so I'm going to assume everyone. Good. You know what's going on, you've watched the videos you're ready to dig into this and and hopefully make some pretty
Josh Moore: Substantial decisions.
Josh Moore: So they were cool keep out of your names. Okay, so there are the four videos so
Josh Moore: We'll and Trevor did a fairly good job. I think of showing the state of the latest latest specs.
Josh Moore: So, so, you know, there are three specs that we've worked on as kind of a community to have those have been posted to image SC and we're still looking for comments.
Josh Moore: I'm in the morning session. We certainly talked about places where those need to be adjusted and then the most recent spec that we've been working on this for high content screening and that's what will show
Josh Moore: Any immediate thoughts.
Damir Sudar: Traditional one. One thing that struck me a little bit is that the respects, of course, tie all together. But there's a kind of a, an overarching statement that says
Damir Sudar: What sub components are needed and and what set what what makes some of them more urgent or to go first.
Damir Sudar: And we
Damir Sudar: Know, kind of like a wish list and then a urgency or
Damir Sudar: Needed needed soon annotation to each of those those things so that link and also as a community can add things that we think are important and others can chime in on. Yeah, yeah. I need that to or mad. I don't care.
Josh Moore: Yeah, so it's something we've held off on to some extent is just defining a central repository for all the specifications and at the moment you you're more than welcome to open so or
Josh Moore: The Tories link the document is currently putting yes open issue against any of those saying I need whatever
Josh Moore: You know, that's where the the conversation certainly could take place, or it could take place on image se
Josh Moore: Um, but the point is very taken. So certainly, the content from this morning. So there were, I think, three or four clear kind of request for a recommendation like specification of polygons, um,
Josh Moore: I guess I can just go, look what they were.
Josh Moore: Gail and origin information on the multi scales that we we put on hold, from the multi scale specification, all of that.
Josh Moore: Compression. All of that will need to show up as individual issues and so
Josh Moore: I'm part of what we'll do, at the very end of this is just talk about how do we keep having these conversations, you know, is it all on GitHub. Is it all a repository. Are we doing it all on image SC, when are we having meetings, things like oh
Josh Moore: As I said in my video certainly throughout the summer, we kind of heads down and just focused on getting a couple of things done. But now with this meeting. It's all about finding out ways to keep the conversation going and make sure that everyone can can get themselves heard
Josh Moore: The flip side of that, though, is it will almost certainly be necessary if we have the community raising issues saying this is vital that we also have more people implementing those issues. So that'll be what I'm requesting right so just be ready for that.
Josh Moore: Anyone else
Josh Moore: Okay so everyone's good on the state of the videos. Everyone give it a try and download anything
Josh Moore: Yeah, we thought about doing the whole live demo thing that's always it's always a question. Um,
Josh Moore: Okay, so in addition to the things
Josh Moore: I can't tell if everyone's happy or you're just quiet, um, for me it sounds like the two biggest things that we have to probably address. And it was quite different from this morning.
Josh Moore: Our basically comes of the software from microscopy paper. So it's actually something I've been wanting to engage with for a while, so I don't know who all was there.
Josh Moore: Um, but I can certainly Express. I have a very different reading of of how this is going to work. And I think the Geneva your crew.
Josh Moore: Are certainly talking to private ish after the meeting chef on private, um, there's this idea that we can do everything with an API. And I think that's one of the big decisions we have to make is, is it an API or is it a file format, um,
Josh Moore: So that's certainly something we can dig into if anyone's interested
Josh Moore: The process data. So can talk about the state of the little images as they stand. One of the requests from this morning.
Josh Moore: Was what how to go about adding metadata on to the current specifications, you know, how do you add the class name for each of the the labels in an image.
Josh Moore: And that kind of went even further in terms of can we add you know if you have vertices that are stored in the in the format. Can you add information to each of the vertices basically at the highest level, the most generic request is can we have tabular data in the format, um,
Josh Moore: And eventually we will be able to, there's actually a problem, supporting it in the same way between czar and in five. So that's something we can always use help with making sure that we shouldn't in the same way.
Josh Moore: And then there's the larger meta data questions which I guess is listed here. Okay.
Josh Moore: I mean, it looks like at the moment.
Josh Moore: It's either multi scale or copying data.
Josh Moore: I think copying data can kind of
Josh Moore: Way, first we want to start there.
Josh Moore: Mark, you want to say something.
Mark Kittisopikul: Sure. So I think the broader question. Well, the maybe the
Mark Kittisopikul: impetus for for that copying data is I think a lot of us are acquiring raw data from microscopes, or various devices and we have to do with somewhere.
Mark Kittisopikul: And then we have to start analyzing or processing it. And so this is starting to become a really big problem is one usually coming up from microscope, you got it in one format either defined by the control software or by the camera manufacturer
Mark Kittisopikul: Or, you know, however, someone brings it together. And then there's a need to either reformat it into something like we're talking about now or or maybe move it somewhere where it's more accessible. And so this is starting to become increasingly type consuming process that both inhibits
Mark Kittisopikul: Us of the instrument, but
Mark Kittisopikul: Also, it just makes it a challenge in terms of being able to get it to the people who need it.
Mark Kittisopikul: And so I think maybe one one caution about kind of coming up with a new format is, you know, now we're adding get one more format.
Mark Kittisopikul: To the whole list of things and making sure that we're not kind of
Josh Moore: Making it
Mark Kittisopikul: more onerous by requiring yet another copy of that do
Josh Moore: You want to add on to that.
Davis Bennett: I mean, the issue that's particular to the trunk formats is that if you have any overhead associated with moving one thing on the file system to another as
Davis Bennett: Soon as you proliferate, the number of things on the file system through Chungking that starts to be an issue that wasn't an issue for tip for HDFS
Davis Bennett: Oh,
Davis Bennett: My experience has been. I mean, I'm, I'm using one like czar. By default, puts all the chunks in a single folder. If you try to open that folder and as a million chunks. You can go get a coffee or something. Is this good
Davis Bennett: Oh czar also supports the nested directory store.
Davis Bennett: And if you want to copy a bunch of things then parallelism is your friend. Both not necessarily obvious to people who are used to a format that doesn't fill the file system but little things.
Davis Bennett: And then another perspective is, if you want to sacrifice. This could be an extension to end fibers are if you're willing to sacrifice atomic rights.
Davis Bennett: Then you could fuse trunks together and make a version of a data set. And this is essentially what neuro Glanzer the web based volume viewer does
Davis Bennett: Dietary format data are stored in chunks. But then there's a compaction step the trunks are there and you have 10 files, each of which is pretty big. But it's easy to copy
Davis Bennett: All of these, sorry.
Eric Perlman: As a yeah Trevor has done some very cool work on this plane with. Oh, I mean, typically find more optimal formats to use, but it's been cool to follow. I think you've been on those sites as well.
Davis Bennett: The I think all of this falls under the new territory and people maybe need to learn new tricks like for me, deleting big containers took a long time so I wrote some code to paralyze it and now it's not an issue.
Davis Bennett: Modern computers have enough cores that I think that just some coding can get around some of these issues.
Bill Katz: It seems like one of the things that this kind of brings up
Bill Katz: Is the notion that with the single you know chump profile versus, you know, the Uncharted versus the shorted representation for example in neuro Glanzer and also immutable versus mutable.
Bill Katz: Because I think those distinctions mean a lot in terms of share ability. How much data needs to be transformed.
Bill Katz: And also raises the question to of API versus file format because if you're doing an API.
Bill Katz: And data engine. You can do a lot of transformation before you actually get the data, whereas if you're assuming that you're reaching directly into a chunk and need to interpret it immediately the file format.
Bill Katz: Then um you know that that limits your options in adding things like transactions burgeoning etc.
Blair Rossetti (Janelia): To Davis this point as well. A we're always keeping the user perspective in mind because while it might be easier for us to write some code to delete this stuff in parallel visitors undoubtedly will just try and click and drag stuff.
Blair Rossetti (Janelia): And anything that slows them down is going to be a headache for us because they'll complain about the past and future.
Blair Rossetti (Janelia): So I think mechanisms that are non programmer friendly are going to be critical, at least from our niche.
Jamie Sherman: From my perspective, and I come from a bit of an outside space and from a mass spec background. Originally, is that
Jamie Sherman: Like the formats that are created by the instrument manufacturers are entirely designed around dumping data to disk as fast as possible because acquisition speed as a selling point
Jamie Sherman: And so they're never going to be optimized for viewing and they never liked having worked for a mass spec campaign. They never spend. They're not interested in spending time
Jamie Sherman: Optimizing a viewer for you eat like a file format for using it. It's purely for acquisition. But so, like, so I think that there is a valid role for creating quote unquote yet another file format.
Jamie Sherman: It, assuming it gives us a user and that we want in from my like the one thing I would love to see or what gets me excited about czar and these other formats.
Jamie Sherman: That are chunked is that
Jamie Sherman: I really liked the idea of being able to put the data like we're trying to share data right and we're trying to share it in an open format.
Jamie Sherman: And if we can put it on, you know, Google or AWS or whatever cloud server and let people actually browse the data in that context that that's incredibly valuable because currently we're already sharing quite a bit of a fair few terabytes of data and
Jamie Sherman: And the challenge we have is that nobody's going to go there and download a couple terabytes of data to browse through it because you know storage things, etc.
Jamie Sherman: And if the if the file format. Sorry part dynamic and we can use you know FF FSS back or whatever to pull the data from, you know, and interact with it through a browser, like a party or whatever.
Jamie Sherman: Then that makes the data, much more usable. It makes it discoverable from experimental his perspective, I think we're. It sounds like there are two kind of target markets here one that's kind of the website and the other. That's more of the
Jamie Sherman: Like the user in a lab who has who's just dealing with the file as an entity.
Jamie Sherman: And so I guess breaking things into those perspectives might be helpful. Anyway, thanks for listening.
John Bogovic: But I have some related points.
John Bogovic: I think, I think those are great points. And related to that, um, my feeling is that
John Bogovic: Hot wallet copying data is important. I think I would like to, I don't know if educators, the right word, but I think users should avoid copying just copying data as much as possible.
John Bogovic: And especially when data gets large enough
John Bogovic: And to that end, I guess I would hope that there is a regime in which these junk file formats just shouldn't be used, that is small to medium sized data just shouldn't you shouldn't have a million chunks of a
John Bogovic: Data set that is small enough, whatever that means. So, I mean, this is I think truths are and probably true been five that there might be a regime in which
John Bogovic: It's chunked into just one chunk and that's it. Is that reasonable. I'm curious what people think about that idea and that is chunk data sets should have a fallback to an unranked
John Bogovic: version that is still viable.
Ilan Gold: I just want to comment that I something I ran into maybe a couple months ago when we were we, I work on the hub map portal and something
Ilan Gold: I ran into when developing our tools. Was that one of the things you can't do a czar that you can do with like a single files. You can't just like download it in your browser. Are you you need
Ilan Gold: Need like utilities to get at that folder structure, I think. I don't think you can kind of just W get as our store.
Ilan Gold: Unless it's, I think there's maybe like a way to do it. But I don't think that, as far as I understand there's not like a way to just W. Get it like you need a command line utility
Ilan Gold: For a cloud provider GS you till or AWS S3 CP so like that. That's maybe another another case where like having both file formats stored be useful.
Davis Bennett: So we'd have to be, I think, fundamental issue is that the metadata is stored in a separate object from the data.
Davis Bennett: Unless you sip it together. There's not one thing you could get that has the whole story.
Ilan Gold: Right, so I brought this up specifically because you said like, oh,
Ilan Gold: You know, it's, it's obviously like possible to do this, but to non computer like if it requires like a little bit of computer science here to be able to like download this utility or use the utility, whereas some users, maybe don't want that. So,
Josh Moore: So I have a couple of thoughts, they're not
Josh Moore: Exactly well structured on this from the only me side I'm certainly and what we did just in the experiments we've done so far with SAR um it's a huge benefit to be able to say
Josh Moore: This thing is is a morphic wherever we put it. So we have the images locally. We work with it one way, the code works identically to if it's remote obviously their performance impacts, but um
Josh Moore: And I actually think with this specification. Well, I think a goal of any specifications, we come up with should also then apply to other formats. So
Josh Moore: You know, in the regime where you would rather have one file use HTML5, you know, that's fine. It's, it's, it's a good format and it you know it has its limits. But all of these things do. It's a trade off.
Josh Moore: Um, I think it would be so it, it's still useful for us to have these conversations about these various conventions, like other communities have done so I'm thinking of the geospatial community where
Josh Moore: There's an entire process where they go through saying here's how we grow and how we're going to represent maps and they've gone through exactly this process. There was net CDF for many years and their data set and that CDF which is HTML5 and now they're moving to czar and free
Josh Moore: Own. Um, and now you know the underlying that CDF library is being taught how to work with czar. So, the two are completely perfect so you know that you're getting everything out of a piece of data.
Josh Moore: Regardless of what store. It's sitting in you know so i i think there's an abstraction here that we can we can use to stop worrying, a little bit about
Josh Moore: The specifics. You know, we want to enable for the user that they can choose one or the other, um,
Josh Moore: But if it's but if you're sure. So what's missing at the moment from bio format is you don't know this, you know, we don't know from the proprietary file formats. If we have absolutely everything is it structured properly.
Josh Moore: But if we've made these specifications together as a community, we can say we want to do this in HDFS
Josh Moore: We could choose a sub sub format of each of HDFS we could choose PTV or Mrs and say we're going to do the single file you case in this container.
Josh Moore: For the cloud use case, you know, we're working to have czar and in five, the same underlying specification. Okay, that needs to be some somehow unified and then there will be one cloud based, you know, small chunk based format and it's all the same.
Josh Moore: So I think, um, it's an involved way of saying, you know, try to keep the number of formats as small as possible, which is what a lot of you mentioned and you know in your intro so
Josh Moore: Maybe it's a question about how to go about doing that if I roll back even farther and start to think about the API versus file format. I guess I have. And maybe it's a naive.
Josh Moore: Hope that we can we can have a format that that is this is amorphous and that we can put anywhere we can store it in any way. And then we start to build up or they expend extensions to the specification that allow us to do some of the more complex API like
Josh Moore: indexing of the data, you know, there are things that are beyond what a file format can do. Um,
Josh Moore: I guess just if if I go to a service. I would like that service to still provide me the base underlying specifications that we've all agreed on, you know, in the, in the simplest way to get it now i w get the entire data.
Josh Moore: But if you're on top of it, by all means, I, why not, right, it may be that some some implementations don't
Josh Moore: Support all of the indexing and I think this is probably a lot. I mean, I don't know much about neuro glance right basically know what Eric has taught me. Um, but I think
Josh Moore: You know, I think all of its functionality can be basically considered an extension to the spec that some communities may need and then we kind of get the best of both worlds. Okay, that was my spiel.
I mean,
Davis Bennett: I would just like I'm used to. I was used to using image VIEWERS LIKE Fiji or image j, then, as a user, you need to think about the file format of your data.
Davis Bennett: Because you need to know what's in the file system. You need to know that can image a read my TIFF file is Jay for a while 64 bit floats for a while. So this was always a headache for me.
Davis Bennett: But now that I'm working a lot with neuro Glanzer it's extremely refreshing then answer has no idea what format format my data is in. And I think a lot of users would actually prefer to be in that situation and never need to care what file format, the data is actually stored
Davis Bennett: They just know where is the data and can my tool stand what data is at that place.
Davis Bennett: So, this I think my experience working with image as an API or image as a service has been it's felt way nicer than image as a form
Davis Bennett: Oh, if the visualization tools will approach. But if Fiji, for example, would stop having an opinion about, you know, different tips.
Davis Bennett: Would delegate actually handling the file format to some other service and would just focus on rendering images that it gets from who knows where I think a lot of these problems spike obviously pushed maybe somewhere else.
Davis Bennett: I
Josh Moore: Still think some of the conversations we're having. We're still gonna
Josh Moore: We're still going to need to have, but
Josh Moore: I don't disagree with you at all.
Josh Moore: Veteran and you have your hand up.
Caterina Strambio: Yes, primary a question.
Caterina Strambio: So the idea is you know I think minimal number of formats. I'm
Caterina Strambio: Definitely obviously very much on board. I'm just thinking, I don't know if we have addressed this issue or if we need to address it here. How do we get from
Caterina Strambio: Here to there because I mean we we know that the manufacturers of the soft of the microscopes and the software that goes with that microscope will not. We want to continue to produce their file formats, so that they in maximizes as as Jamie was saying.
Caterina Strambio: Writing on disk.
Caterina Strambio: It is the idea that we're just gonna
Caterina Strambio: Come up with a great solution. We're going to ask them to participate, a conversation and then present them with a fit with, you know, like a fait accompli like this is what we want to do and come up with it or
Caterina Strambio: Which I mean I don't have any anything in principle against it. It's just, I'm just thinking, what are we, do we need to talk about how we're going to get there in terms of what manufacturers will do
Ulrike Boehm: Think they should be invited as well, right, to my mind, like everyone who kind of works to
Ulrike Boehm: In a slide way on data formats. Also, the developers of current data formats like n five and czar and so on and so forth. They need to be part of this discussion as well because they are actually the people who
Ulrike Boehm: Also know bit more about the visibility whether this type of data formidable how it has has been created is as flexible to fulfill the demands right
Caterina Strambio: Well, the developers of the
Caterina Strambio: ends are and stop their part of it. The question is more like the manufacturer. So just clubs. Anyway, I'll shut up.
Davis Bennett: Is it the many years, at least for light microscopes, they've had the opportunity for years to at least be on a standard between manufacturers. So, as far as I know, it's ice and Olympus.
Davis Bennett: I'll use different formats. So they actually cared about providing something that would be convenient for users, they would have done it.
Josh Moore: So I guess I want to give them the
Josh Moore: Benefit of the doubt. So we've had multiple conversations
Josh Moore: So Stephen can relate Wagner from Zeiss like no Conrad was on the session this morning, you can kind of see his statements, um,
Josh Moore: There were, you know, a handful of vendors five or six at the European bio imaging industry board meeting, I guess, at the end of 2018
Josh Moore: So it's been better than ever before talking to vendors and hearing them say, okay, we could see possibly having a developer work with you guys to develop something we could see
Josh Moore: And some of the statements are well if there's a good C or c++ library then ok we'll, we'll consider where you know we're we're making baby steps towards this. And I guess that's what Catarina is saying as well.
Josh Moore: You know, from our point of view, what, what we can see doing is just trying to get to the point where there's a solid
Josh Moore: Specification solid libraries arm and hope to sell it to them, you know, that's, I don't know anything else to do. It sounds like there's additionally
Josh Moore: The API conversation on top of that, which I think is still interesting I don't exactly know what the vendors will hell, they will see their interaction with the API as opposed to a file format, you know,
Josh Moore: I don't disagree with what you guys are saying, you know, we're very, very file format based and just we've been forced to be for for many years.
Josh Moore: Maybe there's a way to free ourselves to look even higher for a better solution. I still think it will revolve around good implementations good specifications and lots of conversations
Josh Moore: You know, I just assume if we start to look at API's. For example, there will be, you know, there will be things that other communities are going to need to add into that API. And it to the extent that that's doable.
Josh Moore: You know, all on board, but it's still the same process and and maybe we redefine what n g f f is, but it's still the same process of this community and as many other communities as want to partake participate completely agree with Rica, you know, everyone should be on board.
Josh Moore: Of making sure you know we have a process to go if we don't agree if the API or the file format is slightly different in two places. How do we get them unified
Josh Moore: Basically I, you know, Mia culpa I've mostly focused on doing that with czar and in five to date. You know we got money to get someone to work on it. They're working on it, it should be done by the end of the year. I'll cross my fingers.
Josh Moore: And then we move on to the next problem, right. So if any of you know, you know, answering or trying to answer Catarina first question, if you know the next thing we really need to tackle to make this happen. You know, let's do it. That's what this meeting is all about.
Bill Katz: I think
Josh Moore: All of one, sorry. Go ahead.
Bill Katz: So from, from my perspective, it seems like
Bill Katz: You know, I see a lot of the discussion is primarily focused around dense data that we kind of like that makes a lot of sense.
Bill Katz: Because 2D, 3D and 2D image data will be dense and so when you're doing physical partitioning to do like in five and SAR that also makes sense because each of the files are relatively similar size.
Bill Katz: One of the things that I really liked about tile DB, for example, is that they completely differentiate between the physical partitioning and the case for
Bill Katz: sparse data.
Bill Katz: For things that you don't actually you can't easily physically partition, because then you, you want to do it partitioning more based on capacity.
Bill Katz: And so I think one of the issues that I see with trying to standardize a file format is you have to know if the file format would be suitable for the different kinds of use cases.
Bill Katz: And it's not clear to me, for example, that you could get a file format that supports both dense and sparse. I believe in the tile DB case, for example, they have two different file.
Bill Katz: formats for those two different cases. And I think that they're trying to create a universal data format and they think that the dense and the sparse case handles everything so that they can build data frames on top of it, etc.
Bill Katz: But I think one way to approach this might be saying, Okay, what is the minimal set of sort of characteristics of data that we need to support
Bill Katz: And what are the file formats that we believe you know at least suitable for that.
Bill Katz: Because it's not clear to me, for example of you going in five czar route, whether that's even suitable for example, doing sparse volumes, where you're just interested in a few neurons, you know, that are spanning massive amounts of spaces.
Bill Katz: Or if you're doing meshes or other things that. So it really depends on the type of data.
Josh Moore: So agreed. So just as a side note that we have had conversations with tile DB and actually just from aerosol
Josh Moore: Go outside of having some base implement a SAS based format that everyone's using and then building their feet on top of it. So I would hope we could even work with tile dB. I know their, their implementation is a very strong one. So, okay, I'm make use of that and and tie everything together.
Bill Katz: I guess I'll also put a disclaimer here that I'm starting to collaborate with the founder of tile DB on adding branch version to their system, which I think is natural, given the way that they handle fragments and stuff like that.
Josh Moore: So I think I'm good. Go for it.
Ola Tarkowska: But basically I definitely agree with you build that we use cases are crucial to define because I, as I said, on the chat. I found my needed optimization in the file format.
Ola Tarkowska: needs to happen on the process level and it's up optimization is happening for each individual process. So whether it's visualization analysis registration or
Ola Tarkowska: archiving, they require very different data. It's the same pixel data, but different formats are needed to process this the most efficient way. And if we dig more into those processes they they just require different solutions so
Bill Katz: I think we can see that very easily to if you're supporting visualization Apple applications. Right.
Bill Katz: Because the style that it's written in. You almost want it to be on GPU available. So like for example neural Glanzer
Bill Katz: Has as part of their format that he designed a compression scheme for segmentation such that it can be easily loaded, and then you know be altered using shader code or whatnot.
Bill Katz: And so I think that it's almost like in the database world. You can almost see this d normalization approach right that you'd like to have a normalized form of the data.
Bill Katz: But it just is not suitable for a variety of use cases where you're going to want to D normalize the data so that it can be rapidly done and so
Bill Katz: I think that's another aspect because like we're also seeing the the graphics card companies are starting to support things like direct storage.
Bill Katz: Where you can move the data directly from the whatever store you have into the GPU. Um, and so, yeah, these are all things that are sort of part of it.
Josh Moore: I think I missed
Nicolas Chiaruttini: Some other hands.
Josh Moore: Go for it.
Nicolas Chiaruttini: If I can come on. Just quickly on the political side towards the Vandal, I would just like to mention that seeing the microscope each facility. I've also emerging facility.
Nicolas Chiaruttini: They need to have a common workflow for all the Vandals to get something which is not 50 different process to to do the same segmentation.
Nicolas Chiaruttini: And basically in the code for tender. You can we SPS explicitly specify, you want to have the bio format API supported in beauty resolution and so on.
Nicolas Chiaruttini: And this is an argument also to push the Vandals to go to wild something unified so if there is a good specific age good specification, then you can push
Nicolas Chiaruttini: For this other microscopy facility level. So we did this with the microscope. Unfortunately, we did not specify mercury resolution, then we end up with a better format API without mercy reservation and I'm pushing a lot of the people from later.
Nicolas Chiaruttini: Not to mention them that I hope will work to watch this. But just to mention that at the microscope P facilitator, you cannot really
Nicolas Chiaruttini: An impact because when you buy an equipment. If the Vandals see on the court photos and you need to support something at some point I simply they will do it.
Jason Swedlow: A COUPLE COMMENTS.
Jason Swedlow: So say a couple things just from the standpoint
Jason Swedlow: Of our experience.
Jason Swedlow: With respect to the vendors. I think Josh is correct. There's an awful lot of interest. It's fair to say Zeiss has been the most present, but we know
Jason Swedlow: We're getting a lot of attention from Nikon and Olympus, as well as, like, as I've had a lot of conversations high level conversations with like
Jason Swedlow: Probably just to summarize, an awful lot.
Jason Swedlow: This is going to be this is going to be a long process to work through with them and it's going to be
Jason Swedlow: I think just parroting Joshua, it's going to be a lot of talking, but it will be based on what they just said, which is, you know, very strong specifications and if those exist.
Jason Swedlow: They will pay attention and they will adopt them proof of that is we've had anecdotally been anecdotally told several times from settlement manufacturers, they tell the customers to use file formats.
Jason Swedlow: Right, so that's that's kind of an example of that. So that's, that's, that's the first thing that's possibly
Jason Swedlow: A little bit pathologically optimistic. I'm usually accused of being that, that's my role in the project. But, you know,
Jason Swedlow: That put all of that won't happen in the next week. I think the other thing we're seeing is a single format just won't do it and to pretend that
Jason Swedlow: All of the use cases that we're talking about. We're covering
Jason Swedlow: First of all, the modalities that we're talking about the kinds of visualization that bill is thinking about with respect to, you know, a whole brain and I will actually want to focus on two different neurons that are separated by millimeters
Jason Swedlow: public repositories, etc. I mean there's just extremely, extremely different needs and use cases. So the pretense that oh, there will be a single thing out there, it will solve all the world's problems.
Jason Swedlow: Is I think needs to be put to bed. I will tell you, however, that as I kind of slightly jokingly mentioned, you know, I end up having to pay the bills around here, at least for me.
Jason Swedlow: I was on a two hour call with the thunder. And so if you say to them.
Jason Swedlow: If they're if the call is about interoperability and data access and open data and they say, Wait, wait, wait, you're going to solve this by coming up with yet another file format. Actually, no, not just one probably four or five
Jason Swedlow: You know, basically, understanding that is really super hard. And so that gets to be a hard, hard. So we've had some success with CGI. And we're very grateful for that. But the reality is we're going to have to
Jason Swedlow: Work on how we present this actually very serious way not only to fundraise for to our institutions as well. Right. So, I mean, you know, selling this within the various institutions that you all work for is going to be a challenge.
Jason Swedlow: But you know that's that's just part of it. And there was one final point I can't remember what it was. But yeah, I think there's just the reality. Many of the things that we're talking about here are
Jason Swedlow: are reflective of the where we are sorry, the last point with respect to API. I've also the person who ends up having to fund bio formats.
Jason Swedlow: We have a lot of experience in using bio formats and it are in the image data resource, you know, the idea of an API and just random formats underneath is is running out of steam it just it it really is too much to ask
Jason Swedlow: With you know when when driven by the data with the complexity of the data coming in the sheer size is part of it. But part of it was all the other things that we're discussing so
Jason Swedlow: I think any are experienced that. I think everybody on the team agrees with me, if not say so. But we need some kind of convergence at that at that at that storage level.
Jason Swedlow: So that in in in partially responding to Davis's point, which I'm sure we all agree, is that the having infinite divergence at that level is is going is we're seeing that run out of steam so file formats basically can't keep up.
Jason Swedlow: When you're working at scale, right, so that's that's the sheer reality, we see that all the time and it cetera. Sorry. So at several points, but
Jason Swedlow: There will be multiple formats. I think I like, I think it was Josh said, you know, CAN WE NAIL down exactly what are the things that we're going to need
Jason Swedlow: To satisfy this range of requirements so you know Bill's got one end, which is actually extremely important. I mean, that's a key biological problem.
Jason Swedlow: With public data resources have another end have another end several other dimensions to think about there. But, you know, if we can nail those down. I think that would that would really help us decide a half before
Bill Katz: So Jason, if I could comment on what you just said about
Bill Katz: You know the explosion of the file formats. There was a and I probably should have posted the links on that there was
Bill Katz: Two blog posts one by open ML about what would be the ideal data format for open machine learning data sets.
Bill Katz: And then there was a response by the tile DB founder about why they should consider tile DB as a universal data format and it was primarily focused on. And I would say that the one argument, which I kind of agree was with Stavros on is that
Bill Katz: The towel DB approach, which is
Bill Katz: The focus should be on data engines and API's over file formats, because at least with data engines and my data engine. I just kind of mean that it could be a library, which could be like an embedded library.
Bill Katz: Where you don't actually know what's going on. But you, you have an API, you can ask for things and it automatically figures out
Bill Katz: How to get the information that you need, or it can be an HTTP API or some kind of service, which also gives you that ability to kind of like
Bill Katz: You know, change everything on the back end. Fine. You can change the file formats, but your request on the client side won't change and
Bill Katz: So I i think that that was the tile DB approaches that we should focus on that kind of effort and I'm curious because it almost seems like that might be an interesting you know place to start thinking about it file format versus data API embedded engine.
Jason Swedlow: So just to say, I mean, looking at the, at least from the group that I know I think Melissa and Aaron had the most experience with Tyler DB. So, Glenn ko's file formats to raw converter already support style to be
Jason Swedlow: misspeaking so Aaron's it's not so yes it is something we're definitely looking at
Bill Katz: I mean,
Bill Katz: The interesting aspect is that we're already kind of seeing this in that there's a number like for example the end five implementation apparently supports czar in the back end design, implementation in
Bill Katz: Supports and five that you have tensor store now and what Jeremy's doing with neuro Glanzer is he supporting
Bill Katz: My god, he's supporting David boss, you know, a couple of other connectomics APIs as well as pre computed as well as in five and czar. And so what we're why you know what we're seeing is that the
Bill Katz: That the data engine, the embedded libraries are basically doing the job of like figuring out all the file formats.
Josh Moore: We so we should probably. So this sounds like something we should do a breakout on and I mean I'm more than happy and take time and
Josh Moore: I'm even in the next, you know, days or two. My experience has been when you start this eventually you always get back to the question of who's taking the responsibility that biopharma it's currently has it doesn't go away.
Josh Moore: And currently we have it. We're trying to get rid of it. And it's going to fall on someone else if we don't solve this, if we're trying to be good about this right and go, you know, you want to get rid of this. No one should suffer the pain.
Josh Moore: It always becomes as long as you have a number of implementations and I've worked heavily with the in five czar and the czar in five implementations and they have the same problems, they don't
Josh Moore: It's all hard coded at the moment. And it's just barely working. So we need a better way, whether it's the engine or a format where we're definitely not there yet. Sorry, dumb year has really been struggling and then Catarina
Damir Sudar: You're probably asking the same the same thing or proposing the same thing. And so this is pretty much by the
Damir Sudar: Way the separation is to the carbon part of the storage format, whatever its file or API or whatever. And the, the implementation of white pixels. Go. So if we can think of moving as much of the thing that should be as common as possible into the meta data layer and as little as possible.
Damir Sudar: In the implementation of where pixels go layer then potentially we we can move as much to a common, common API or file format as
Damir Sudar: As we can achieve. And then it becomes maybe a little easier to just swap out that pixel storage layer underneath.
Damir Sudar: When it's needed, or have support multiple ones if that's really how it needs to be. And clearly from the discussion. It needs to be that way.
Damir Sudar: So, but push as much as possible into the metadata layer, which should be common and there should not be multiple versions off or multiple access points to
That
Caterina Strambio: Can I speak.
Josh Moore: My mic was awesome.
Caterina Strambio: Okay, now I just wanted to
Caterina Strambio: Just a point of clarification for me.
Caterina Strambio: Maybe others. So we're talking about, you know, the combination. The, the, kind of the dichotomy between API versus format.
Caterina Strambio: The but I'm trying to understand. So if we would have multiple because we decided that there is not going to be a single new format. So it's going to be next generation file formats.
Caterina Strambio: Then there will be API between those
Caterina Strambio: So not. I mean, or not. Am I am is understanding something
Josh Moore: Maybe
Caterina Strambio: They will, they should be translation. I mean, if we decided there is that needs to be more than one
Josh Moore: From our side. Yeah, they will. If there are multiple formats in the oil me space, you will have to be able to translate between them. So that's a given. So from the API side.
Josh Moore: I don't know is does everyone feel comfortable that there's one clear API that represents all the needs and you don't need to map between multiple API's. I find that
Josh Moore: Amazing but
Davis Bennett: I think for dense image data that's reasonable.
Davis Bennett: Like if you think of
Davis Bennett: An image as being a
Davis Bennett: Script of pixels. The job of something, some software that consumes the image is just to ask for some region of pixels and it gets the values back
Davis Bennett: Then a separate query for metadata. I think that's abstract enough to cover any 9% of what people do what what applications do that consume dense images are stuff and other things I think is
Josh Moore: More calm. Yeah. So I think that's an extra call right so
Bill Katz: Yeah, I think that usually as
Bill Katz: Multiple API's where one API is particularly for a particular use case. So for example, you might have an n dimensional array API.
Bill Katz: Or a multi dimensional. I mean, sorry multi scale multi dimensional array API. And that serves you know most of what you might need for in the image format. But if you wanted to do, for example, like a log
Bill Katz: API that might be a little bit different and the format of the data might be different, like if you just wanted to replay all the commands are all the issues. And so, but one that's one of the other things, too, is like
Bill Katz: What is the characteristics of the data and how would you have an API. What is the minimal set of API is necessary for the data that we need in science.
Ola Tarkowska: I think to answer your question is minimum API could be the one that describe data life cycle.
Ola Tarkowska: Because we speak a lot of about data but data life cycle could be also taken today account where we actually that this defines the purpose of each workflow of the, you know, of the process, how data is transformed, if that makes sense. This is different approach.
Bill Katz: I mean, to be TV more concrete about like systems that we have to to make on our side.
Bill Katz: We have a different API and a dip in and supported by different data type for three dimensional annotations. So for example, if we need to do synapses.
Bill Katz: Those are a series of 3D points that are sparse. They may have characteristics or properties associated with it, like they're associated with a label or
Bill Katz: That they're considered pre synaptic post synaptic etc. So, so, but that's a very different type of data that may be extremely large like you could have 100 million of these data points is more like a point cloud.
Bill Katz: kind of scenario. And then we have a different data type in a different API for our n dimensional dense stuff. We have a different API. If we wanted sparse volume representation. So for example, if you needed, like a neuron that stretched over large periods of, you know, space.
Bill Katz: In each of these also in terms of like how you'd want to store it might be stored differently because you know they're there are different approaches.
Davis Bennett: I might want to make might be a historical point. But I think what's unique about the types of data that we work with thinking about microscopy data.
Davis Bennett: Is that I don't think private industry has needed to solve the problem of sharing and interrogating enormous by Crosby data sets.
Davis Bennett: So unlike a situation like a database for records database for transactions think these things, these things exist in industry good technical solutions there.
Davis Bennett: But I feel like really large images that come off the microscopes. We use there's there's no precedent, I think. So, we will have to come up with something
Davis Bennett: On our own for other things like the point clouds, maybe best solved with tools that already exist that have been solved in other domains.
Mark Kittisopikul: Oh, let's say I was funny. Maybe try to verify something about API is is I think many of the APS we work with are also bound to a specific program language.
Mark Kittisopikul: And something Davis and I have talked about in the past is maybe moving towards more of a a service model where maybe something like a web service, even where you're more speaking protocol.
Mark Kittisopikul: Or Can think of something like a mirror.
Mark Kittisopikul: So you have a server that's a couple actually parse whatever format you want and provide you the
Mark Kittisopikul: pixel data.
Mark Kittisopikul: And so that's that's another thing. The other thing I've noticed and talking to some manufacturers is there's some willingness to support
Mark Kittisopikul: Support the users if they could be provided some kind of interface.
Mark Kittisopikul: So for example, we were talking to Karen manufacturer about maybe using kind of block based format. And they said, Well, you know, just send us a DLL
Mark Kittisopikul: And will we, you know, we'd be willing to plug into that.
Mark Kittisopikul: And so I think there's there's someone has to maybe think of
Mark Kittisopikul: Some kind of modular ecosystem where, you know, we can define
Mark Kittisopikul: Maybe abstractly, the interface of there might be some willingness to build modules that connect to those interfaces.
Mark Kittisopikul: And I guess one other point about API's. So I think that, you know, there are some, there's some of the things that we need to be aware of in terms of the legal aspects of using API is is currently working as a way through the US Supreme Court.
Mark Kittisopikul: Specifically kind of with the Java or Google or support local matter that we need to be cautious about and making sure that we do provide these interfaces that we make sure that they are free to use
Josh Moore: Dummy
Damir Sudar: Sorry, I forgot to lower my hand. Sorry. Okay.
Josh Moore: So wherever we ended up
Josh Moore: Sounds like we certainly need so from my side. I mean, it probably means an investigation and maybe a learning experience of the API's that exists. So if anyone wants to, you know,
Josh Moore: Volunteer to either teach me directly, or maybe set up a little lightning talk and walk us through it. That would actually be really valuable and would help me understand, are we actually seeing the same thing. And we're just seeing it in different ways, or
Josh Moore: Are we in two completely different worlds or I think the most likely, and I think the most optimal. You know, is it, is it a subset, and a superset that we can actually work together quite nicely. That'd be my hope I'm
Josh Moore: So that's fair.
Josh Moore: We still have a couple more topics that we have about 45 minutes so you wouldn't want to Buddhist to something completely different. So we try to make
Josh Moore: kind of wake up. I actually was warned that in the previous session, we should we should have built in a break. About half. So the next time we have a call. I'll build into the schedule. So at least a few minutes to get away and get something to drink.
Josh Moore: Mean next on the list of most people who are interested was actually just talking about the pyramids in the multi scale representation. Is that still valid. Does anyone have any particular. They want to know. I want to share about those
Davis Bennett: I just want to say I'm excited about the army specification
Davis Bennett: Cool one I am thinking about asking the Neuromancer developer to support that, because I don't. He has implemented any pyramid specification for czar containers, maybe Eric Perlman can speak to that.
Eric Perlman: I can speak to that, that he's support Jeremy has support for Saul films original sort of hacky and five scale down samples.
Eric Perlman: Like whatever it was. That's all felt that additionally with the FBI data judge john is very well aware of. He supports that. And so one of the things I've talked to Josh more about is it would be straightforward to
Eric Perlman: Add a dialect of that using for the Tsar data source. I mean, basically, we just copy and paste the five as a sample. The bigger issue of neuronal answer is actually that he currently requires
Eric Perlman: All the dimensional dimensions be in the same chunk. This is not an issue if you're doing DM data, but to be an RGB data currently at the moment in the LM a world like a bio formats to raw
Eric Perlman: RG and be an alpha are going to be four distinct chunks.
Eric Perlman: And so when I have done this, I have to write to disk and then reformat it to the right size but Jeremy's. I mean, it's one of those things where, unfortunately, Jeremy is the only one in the universe, who could
Eric Perlman: Fix your answer to support that so well. So anyway, that's probably something to ask him.
John Bogovic: I'm also just I'd like to say that I'm excited and I hope we agree on what we do about pyramids in the future, but that's essentially all I'm okay. If we move ahead.
Eric Perlman: Yeah, I mean the pyramids basically been two dialects. There was the model of for each resolution you say what the new resolution is versus the other dialect, which is for each resolution you say how much it was down sampled
Eric Perlman: I mean, they're fine functionally the same but it's been kind of those have been the two camps.
Josh Moore: You just kind of have to make a decision at some point. So for anyone who wasn't part of it. So there was actually a quite protracted conversation on GitHub. I mean, if you follow the links from image SC, you can get back there. So all of that's archived right for posterity. Um,
Josh Moore: So from my side. Yeah, it was, it was good to just get everyone to agree, make a decision, say this is what we're going to do going forward.
Josh Moore: Um, the more pieces of software that we can get writing reading and writing the same format, the better. So if anyone's blocked in any way on making that happen. Speak up. And let's try to tackle that
Josh Moore: Sounds like we need time from Jeremy. So, okay, I don't know what what has to happen for that to occur. Maybe its funding. I don't know.
Josh Moore: I'm from my side. I do know that and one was talking about that this morning.
Josh Moore: You know there's we we punted on the scale factor. The scale origin and offset metadata from the multi scale specification. I assume that's blocking some people and so sorry john I'm so whoever would like to, you know,
Josh Moore: I have a couple of things more things on my plate. But if someone wants to go. Okay. You know, I have an opinion. This is how we should do it basically
Josh Moore: Bringing back that conversation from the Tsar spec repository that would be a great way to make it happen. So basically we need
Josh Moore: To run the conversation a little bit, get the consensus, again, I think the implementation is easy. You know, it's not really a problem. Once you've made the decision.
Josh Moore: And then we go from there. So maybe we can get that done during 2020 that might be a nice way to kind of top off the year, um,
Josh Moore: Nico, you're
Josh Moore: Raising your oh actually several hands Nico then Trevor then Jamie, sorry.
Nicolas Chiaruttini: Maybe I missed what you're talking about the description retailing the specification that happened somewhere on GitHub.
Right.
Nicolas Chiaruttini: Okay, so then, yeah, I just put a link, because then I would be interested to see
Nicolas Chiaruttini: Regarding mercury resolution. So I don't know, I just use the bio formats API, which is working fine. And I did a bridge with a big data mover.
Nicolas Chiaruttini: So, which is like an iframe transformed from different scale what I was wondering if you discuss this matter is when you do reduction of show pictures towards one hour block.
Nicolas Chiaruttini: Usually you compute the average of the pizza.
Nicolas Chiaruttini: So then you get the average of eight pixels or whatever. But then I was wondering whether there was a possibility or it needs to be specified
Nicolas Chiaruttini: Whether you want to do rejection with the maximum value. For instance, or with a minimum value or with something different. So meaning specifying the process by which you're reducing
Nicolas Chiaruttini: The scale of your object because I found that it's an issue perform on his average
Nicolas Chiaruttini: Then your structure when you downscale lot then basically you have Reggie zero but issue. Do a rejection with maximum value then you end up with a sort of maximum projection in three. So I don't know if I'm clear
Josh Moore: I think you're beyond me, but I think
Josh Moore: We should try this, you know, is
Josh Moore: There something that you want to see in the spec, like there's a way, you know,
Josh Moore: Depending on what algorithms being used to do the down sampling
Nicolas Chiaruttini: If you want to store what you did.
Josh Moore: We just needed. We needed example basically of what you would like to capture and then let's try to work it into the spec so
Eric Perlman: That would be a great thing in the spec. I mean, I can think of averages max and then also there's the majority down sampling for label data masks.
Eric Perlman: So yeah, I think basically that should be added to that conversation on get how that that's something that should be in the spec. It's probably again one of those things which most people will not use most people will be doing
Eric Perlman: Average down sampling, but it's good to have that meta data stored
Nicolas Chiaruttini: For 3G display, then the maximum taking the maximum pixel out of a chunk can be can be useful for 3D representation of downscaling it, but I can, yeah.
Eric Perlman: I completely agree. By world lately has been series of two dimensional down sampling. So it's not as important, but I totally agree.
Josh Moore: Okay, I think we're on Trevor. And then, Jamie.
Trevor Manz (he/him/his): All right, and bring it the brilliant, but not quite on multi scale anymore, but I have them a little bit of
Trevor Manz (he/him/his): There was a little bit of discussion about, you know, potentially storage types, not being so much like thinking more in terms of data API's rather than format.
Trevor Manz (he/him/his): And I have done a little bit of experimenting with that of using sort of dar as a as a data API layer, rather than and expose like basically using a small micro service.
Trevor Manz (he/him/his): To translate chunks from other format to czar so that our web applications can do it. And I guess my comment is just that there are possibilities to have sort of a data API that mirrors some native format. But also, you know, have all these different types of binary containers as well.
Trevor Manz (he/him/his): But I have done a little bit experimenting with that. I just wanted to comment if anyone wanted to follow up or any question.
Josh Moore: Yeah, I have great hope and what Trevor's been doing so.
Josh Moore: Very cool to make everything just turned into a czar. Go for it. Jamie
Jamie Sherman: Okay, just to two questions, or one question. One comment.
Jamie Sherman: So one is with the pure with a different pyramid data.
Jamie Sherman: Is the general practice when you're pulling from a raw from an instrument manufacturer format to just mere over there are other parents like I'm working. I work on one library that does this. And at the moment I ignore anything that's not pyramid zero and so like
Jamie Sherman: When you're mapping to a common format is this is the general practice to just say, Okay, I'm going to take
Jamie Sherman: Pyramid zero and document how I transform it to a different pyramid level or is it to take the manufacturers image format.
Jamie Sherman: As like it's whatever other pyramid levels that they've encoded and pull them across and put them in the data because I'm a little concerned in that case that you then end up with this like
Jamie Sherman: Yeah, I got this out of something that uses a proprietary like where the information on how it was generated isn't necessarily shared
Jamie Sherman: And so that's that's one kind of common question.
Jamie Sherman: And then the other one is, and this is just because it's come up in this documenting
Jamie Sherman: Down sampling and that kind of thing. I know that there are people at the Institute. I work on that are working on essentially ML transforms where you take lower resolution data and you try and up transform the resolution using an ML algorithm or something like that to
Jamie Sherman: Their pros and cons etc of this kind of methodology, but being able to like link to the method or encode that this isn't actually the raw data or that it's a transformed form of data that would be helpful later it's something to be aware of and think of at least
Josh Moore: Melissa, you want to take the bio formats to we're all
Jamie Sherman: Part of this
Melissa Linkert: Sure. So I'm to your question about whether we, you know, transfer over the any proprietary pyramid that was in the original file, we do not at the moment.
Melissa Linkert: We only take the largest resolution and then it's down sampled from there for all of the reasons that you mentioned, you know, we can't really rely on
Melissa Linkert: How that pyramid was generated. It may not be consistently down sampled across resolutions. So you may have different sizes it between different pyramid levels. It may not be down sampled
Melissa Linkert: You know, at the skill that you would like to see in your final output file. There's just there are all sorts of reasons why it's unreliable to do that. So we just throw everything except the largest resolution away.
Melissa Linkert: We do in both formats to raw document or include in the metadata. The down sampling algorithm that was chosen
Melissa Linkert: There's a few different options for the most part, were using open CV to kind of do the heavy lifting for all of that but whatever algorithm you choose. That's going to be recorded in the metadata that winds up in the bizarre or and five container there.
Melissa Linkert: Excellent.
Melissa Linkert: Thank you.
Josh Moore: And then, in general, I think, you know,
Josh Moore: Several of you have touched on all kinds of things that could go into the metadata. Eventually, um,
Josh Moore: We're currently trying to keep things as simple as possible. You know, so we're not going to try to specify upfront. You know how to store the ML model that you're using to do the down sample or the up sampling
Josh Moore: Um, but I think those are interesting conversation. So from our side, we will try to get an infrastructure in place that allows the metadata to be written down.
Josh Moore: In these formats and access via these API's and then and then all hell's going to break loose right but it's going to be fun. And that's what we need to do. So we'll get there. Davis I think you raised your hand.
Josh Moore: Oh, you're muted.
Davis Bennett: So I, I'd like to offer a contrarian perspective and maybe thinking pessimistically about putting the mechanism by which the data was generated in the multi resolution metadata.
Davis Bennett: Like I it's not what the specific use case is for knowing that it was the mode or the mean and then I worry about
Davis Bennett: The possibility of arbitrary. I mean, you can imagine arbitrary function that eight pixels and generates one pixel out of that. And so there will need
Davis Bennett: Touches for this metadata field if somebody can't generate a string that someone else understand that they use to generate the down sampling
Davis Bennett: So my philosophically my perspective has been a multi resolution pyramid literally just is a collection of images that should be able to stand on their own.
Davis Bennett: And it's some application somewhere that thinks this thing forms a pyramid. But for me, the guiding principle was in the metadata.
Davis Bennett: metadata that describes that image where it is in space and nothing else or arbitrary that could apply to any image. So that's, that's just me being contrarian, though. Yeah.
Josh Moore: I think you're expressing what I'm trying to get out as well as I don't want to be the one responsible for it. I don't have a problem, putting a place where people can fill this out, you know, put something in there. But will the community know how to interpret it.
Josh Moore: I guess they have to decide.
Josh Moore: Okay, any other general theme of feelings on the multi scale representation
Josh Moore: Sounds like we've somewhat segue into metadata. There are a couple people who have their names on it. Any thanks john
Josh Moore: Any immediate thoughts Nico, you are first
Josh Moore: The spline worked
Nicolas Chiaruttini: On. So you just because we have this very big, huge images.
Nicolas Chiaruttini: We don't want to receive them when they are transform and my application is like brand slice registration. And so I want to basically have a mercury resolution image.
Nicolas Chiaruttini: I'm doing nothing and transform spines transform using your John's a big walk thing. And I just want to store the transformation. And so we can be like a few long points, then it's a very concise representation of a transform and I don't know if it has to be supported or not.
Nicolas Chiaruttini: I think I find transform is very important to get the localization in in 3D.
Nicolas Chiaruttini: That would come and add, I think that that should come with a time at which it was taken also time and space. That makes sense.
Nicolas Chiaruttini: But then on top of transform. I was wondering whether we want to support sort of stoned out spline deformation meta data.
Josh Moore: Is your hands up. Davis, or that up again.
Damir Sudar: Go for
Davis Bennett: Yeah, I would once again the the space of possible image creation is so huge.
Davis Bennett: Very that if suppose you do support field metadata field for this specific type of image registration.
Davis Bennett: Consider what fraction of images would field used. And then how many other registration modalities. There are like in the store a warp field. If you've done like a full, you know, a full nonlinear registration.
Davis Bennett: I feel like image registration is like, it's like the medieval map where there's the ocean dragons, like the prospect of supply anything more than linear methods.
Davis Bennett: That apply to the whole image makes me nervous. But maybe if there's something that 99% of images would would use it and the pain of not having in the metadata would be acute.
Davis Bennett: Persuaded in the other direction. That's just my feeling
Josh Moore: John
John Bogovic: unmute. Okay. Yeah, so I think
John Bogovic: I appreciate that we shouldn't define exhaustively all of the metadata that will ever be used like
John Bogovic: Josh or me or no one should be responsible for everything. But whatever format, whatever we decide, should be flexible enough that one can include their own metadata.
John Bogovic: For their own specific needs, because if we don't people like Nico or me or somebody else are going to need or want something and they're going to leave for another format or write a new format with this metadata.
John Bogovic: For their particular purpose. So not every tool has to understand how to use
John Bogovic: The spline that Nico writes into there, but they will be able to at least get the data out whatever data are there, they will be able to get out.
John Bogovic: That is the data that are common. So I'm just, I like to strongly advocate for being as flexible for custom fields with custom content that not every tool.
John Bogovic: Has to be able to read or write or understand whatever Nico or me or whoever writes into that should be documented by the user or creator of the tools that consumed that
John Bogovic: But, and the fact is that if it's if it's written in a common way it will make it easier for other tools to potentially get it out like if it's much easier if say
John Bogovic: Someone in Python wants to use something that Nico writes it will be easier for them to get at the data if they use the metadata of
John Bogovic: Formats FOR THE WAY TO STORE AND READ A meta data, then it would be if Nicole wrote his own format. And that's one of the main reasons I think we should be flexible.
Ulrike Boehm: So so john I completely agree with with like be having the flexibility. But one thing we should all also
Ulrike Boehm: All agree on is like really having a proper documentation that people really in casing need something new, they want to work with something else that everything's really
Ulrike Boehm: Listed in such a way that you can find your way around. And that I think is, I mean, independent of whether there's a diversity or so or as like diversity, it should should be so that people
Ulrike Boehm: I mean that there's no people don't become desperate or so, and they should be also clear what's written in a documentation should because sometimes people define that whatever right like
Ulrike Boehm: But it should be so that people can really also make use of that document, but just as a my two cents.
Bill Katz: Here. It kind of reminds me
Damir Sudar: I think I our next sorry so
Damir Sudar: This is again a
Damir Sudar: Push for the the parallel metadata storage storage discussion that's
Damir Sudar: A nice as leading that in there. What we're trying to do is to have a basic set of metadata fields predefined and actually manage those, and have we really
Damir Sudar: solidly defined and documented as they can to set, but then there is the possibility of extensions. Right. So the idea what Nico needs. Maybe it's just an A fine transform store.
Damir Sudar: A lot of people need Justin I find transform that can be part of the the base metadata definition. But then if you indeed need some weirdo spline transformation that isn't captured
Damir Sudar: Or isn't easily captured in a standardized way the extension mechanism within the metadata environment allows you to store your
Damir Sudar: weirdo registration thing. So, so the idea is to have both, but to be never gets into the point where people say, man, it, it won't help me, and so I'm writing something completely different. So I'm completely on board with with what john just said.
Damir Sudar: So that's it. Thanks.
Jamie Sherman: Jay, okay, so like one like Davis's comment really made me think, and I
Jamie Sherman: Think he's got a really good point. And one of the things that might be key to it is like having a binary fly essentially equivalent of a binary flag that says this is actual raw data.
Jamie Sherman: And everything else is an interpolation interpreted data level.
Jamie Sherman: Would be incredibly useful because then if you're an a naive user, you can just say, all right, I don't have time to evaluate what these other layers are or to derive how they got there.
Jamie Sherman: But I just want to pull all this data in some model or something like that. And I want to know that it's real data without artifacts, then
Jamie Sherman: You can you can find that easily in a trivial way and then obviously having, having the ability to add detail is great, but one of the things that does come to mind is like
Jamie Sherman: How much of this do you want to be like, how much of an open format is cataloging what's been done to acquire the data. So it can be shared.
Jamie Sherman: And how much of it is a lab notebook that's trying to capture everything that ever happened to the file which is kind of becomes a rabbit hole that can go on forever. It's that's just definitely a concern, anyway.
Josh Moore: Just from my side, I would say, we would just put, you know, we'll just give the user paper and then from that point, they have to figure out what they're writing down so
Josh Moore: It was back to Davis.
Davis Bennett: Oh, I, I took my hand down, but I can
Josh Moore: Bill is waiting as well.
Davis Bennett: Sorry, it's just that I was just wondering, is there a way, if you're like a to have metadata. That's like for these extensions. Is there a standard not
Davis Bennett: A specific tool like say neuro Glanzer or big war or whatever to have its metadata registered somehow. What's the state of the art for that.
Josh Moore: So I have an opinion here. I mean, and this is basically part of what will come up in Catarina is call on the 20th, um,
Josh Moore: How far do I want to go in this so
Josh Moore: The experience with me XML has been that XML SSD doesn't or sorry yeah SSD.
Josh Moore: doesn't provide what we need for the ability to extend so basically Catarina went through this huge process wrote a full extension of only the XML.
Josh Moore: And the cost to everyone would have been so high, to actually support it. Right. I mean, it's basically this huge breaking change.
Josh Moore: So my feeling is that JSON LD is the path forward and I have some work to do to make that proposal and show it to everyone. So that's on me and hopefully the person we hired to do this, um,
Josh Moore: That's so the the major competitor to that would be JSON schema. I'm pretty
Josh Moore: skeptical of JSON schema. At this point, after having spent over a year on the human cell Atlas project trying to use JSON schema for this.
Josh Moore: Basically you have all the downsides of XML schema and none of the support that was built up by the W three see over you know decades.
Josh Moore: The RDF our JSON LD community is WS three standardized does have a lot of support. I don't think the supports. Great. The other major downside is it's possible to write things that are very difficult
Josh Moore: To understand so i think i. So, my ideal would be if we could find a way to have some subset of JSON LD.
Josh Moore: I mean, we already want to put JSON into czar right so that's kind of pretty straightforward and then say this is the subset of JSON LD that we're going to support
Josh Moore: One of the key values of it is its extensive ability. It's an open world model, you can always talk about anything. So basically,
Josh Moore: From as the point of oil me currently. So as you know, as it when we we we are the the gatekeepers. We keep people out of the specification
Josh Moore: By force, you know, we just, we can't let anyone write whatever they want.
Josh Moore: The open world model is exactly the opposite. Anyone can say anything they want. So I think that gets us exactly the sensibility that we need
Josh Moore: Um, will end in ultimate chaos. I hope not. I'm that's certainly my word bill on this, let Katarina speak since I talked about her and then get back to you. And then we're slowly need to start wrapping up
Caterina Strambio: Yeah. So I mean, yeah, so there is going to be follow up on the discussion on on the 20. Well, I think it's going to be on the 20th of November, but we still have to finalize any way you can look it up on images see
Caterina Strambio: But, um, yeah. So, I mean, I think that method I didn't jump in because the meta data problem is like there is multiple things that are defined meta data and the one that we have worked on. As for the end initially for the nuclear munition in then Bina, and now support of quiet.
Caterina Strambio: With with the mirror and Enrique and other many other and several other people is the microscopy. So hardware settings quality control part
Caterina Strambio: And the reason why I mean there was a need for the community to
Caterina Strambio: chime in on what is currently being represented in the 2016 version. And we used the access D because that was the that time.
Caterina Strambio: The what was how the mother was represented and but obviously these all along. We've been very interested in moving past that. So,
Caterina Strambio: First, I mean, it is also one of the topics that we will discuss is, you know, is it necessary to have multiple representation. And how do we make sure that they keep
Caterina Strambio: They keep, you know, align with each other.
Caterina Strambio: Anyway, so, um, I don't want to take too much time in in this space. I mean, we can talk about it more
Later.
Caterina Strambio: But anyway, um,
Caterina Strambio: I think that the representation of the meta data is a little bit of a convergence between a couple of different world. One is, what do we want to represent. And so, for example, the community that microscopy community.
Caterina Strambio: Has to chime in on what needs to be represented for the fried defining the hardware and the settings and the quality control versus how do we are presented. And so, you know,
Caterina Strambio: Having different presentation has been necessary for our work because different people. Not everybody can look into a access the file or even in the JSON LD file. So we need a way of for people to interact with the content and
Yeah.
Josh Moore: Okay.
Caterina Strambio: Oh, absolutely, that that has to be human readable.
Josh Moore: So I'll add the link to cut arenas image SC post. And then below that you wanted to say.
Bill Katz: I just had a question, mostly because it was prompted by what Nicholas was saying where, you know, there was this basically custom transformation this, you know, and
Bill Katz: Sort of tying it into compression as well, that if you have an extension or some sort of customized way of, you know, that, that the data actually has to be run through something else.
Bill Katz: I assumed that because I'm not that familiar with all the different types of metadata. Is there something similar to like what we would do with
Bill Katz: Source Code packaging where there's like a UI or something that corresponds to a particular you know like a unique identifier for an extension code base that that would have to be sort of, you know, a plugin that has to be accessible so that someone could actually get the data.
Josh Moore: So at the compression level. Yes. So currently it's fairly hard coded in the V2 spec of czar on the next version of czar that everyone's working on
Josh Moore: Does have a more formal. I think pearl based extension registry so you you know you you get a pearl URL that's the the source of your
Josh Moore: Probably shared library or in Python, you know, just code that you can load and that does the the filtering, or the compression or you know whatever process, it is you want to apply to every chunk.
Josh Moore: At the metadata level, at least in the JSON LD world you have the concept of a context. So you should be able to go to a URL online and load a definition of the metadata.
Josh Moore: Whether or not you can interpret that representation basically depends on how smart your client is, you know, how much do you understand the vocabulary.
Josh Moore: Arm so you know you could imagine if we stick to just the transforms
Josh Moore: You know, if the I think DOM, you talked about a base transform class and I find transform subclass. And if there's a spline subclass that lives in a different context.
Josh Moore: All the fields that are common amongst those you could interpret and maybe do something with them. But you'll need to have the concept of what's a required
Josh Moore: You know, is this useful to me if I don't understand all the metadata. It gets it gets very tricky. Very quickly, as James is pointing out. So I don't know if we're going to be able to build clients, which can work with partial information. Not sure.
Bill Katz: Is there any notion of sort of an extension perhaps being a service as opposed to a link to a piece of code that gets downloaded needs to be executed.
Josh Moore: Only
Bill Katz: There are lots of like landers and various other things. Now, which are available.
Josh Moore: I don't know of anyone who's doing that, but that doesn't mean it's not possible. My, my knee jerk reaction is I have security concerns that sounds actually quite scary.
Josh Moore: Um, but yeah i mean i the security issues can be handled with enough complexity with enough, you know, infrastructure. So that's something to think about.
Josh Moore: Did anyone else have anything to kind of close up.
Josh Moore: Okay, I'm gonna write down
Like I said,
Josh Moore: No URL as a service.
Josh Moore: Okay, so
Josh Moore: If we're kind of in finishing up mode.
Josh Moore: There's certainly a sense that we should figure out next steps. I don't have them off.
Josh Moore: The tip of my tongue. If anyone has anything that they're clear they either want to do this or they want to meet up with someone and have a conversation, feel free to say it now right into the document.
Josh Moore: Otherwise, I will certainly write up a summary of some form and post it to image se or two that will me website. Um, and we keep the conversation going.
Josh Moore: So does anyone have anything they want to do right away.
Josh Moore: Thank you.
Ola Tarkowska: So I have a proposal if it depends on how how extensive your notes are but because today. There were plenty of problem raised and quite a lot of
Ola Tarkowska: Sick basically significant knowledge was shared and I feel there is quite a lot behind this as well. So I was wondering if people would be willing to write some
Ola Tarkowska: Contribute to this specification. Like, for example, like gathering requirements like Moscow method is doing so provide what master would shoot
Ola Tarkowska: What could be there or what you don't want to see based on your experience modalities various instruments you are using various analysis techniques and
Ola Tarkowska: Is this something people would be interested to write down to contribute to
Josh Moore: It from my side. Certainly, going back to I think where we started.
Josh Moore: I don't have. I don't have the URL for you.
Josh Moore: Welcome to take suggestions. But from our side. I think the output of everything we discussed needs to show up as issues. And I feel like with the two sessions we had
Josh Moore: There's at least a good doesn't highlight, we need to think about. And then all I guess what you're proposing as a form of not voting on those but categorizing them in terms of
Josh Moore: Priorities yeah
Ola Tarkowska: Yeah, but this could help you have to decide what actually API should have and must have what's up show now and what shouldn't be there. Based on the use cases and experience because this was right. Since the beginning that we should operate on workflows.
Ola Tarkowska: Well, it's up up to everyone. So it's just a suggestion. This could highlight
Ola Tarkowska: Lots of good things.
Josh Moore: Yeah, so I think something like that definitely needs to happen. I'm a bit
Josh Moore: unclear what's the path forward to make it happen. I mean, we're all busy so that'll be the biggest trick I'm
Josh Moore: Okay. So, kind of in that vein, so now I'm just going through the we have nine minutes. So the next step topics that I listed
Josh Moore: I assume everyone's okay with
Josh Moore: publishing the notes. They've been public
Josh Moore: publishing the recordings. I'll get all that online.
Josh Moore: Lots of thumbs up or thumbs down.
Josh Moore: Is there a general feeling that it's worth doing this regularly.
Josh Moore: So I asked this morning as well. So in roughly a month.
Josh Moore: So I hope from all me side that will some more results will do another video or two.
Josh Moore: I mean, I can just throw it out there and image se and whoever shows up shows up. So that's fine if there are particular discussions that someone wants to happen.
Josh Moore: Not month period somehow say the word either now or in the document or an image se when we say, you know, when I opened up the registration for the next one.
Josh Moore: Anyone's welcome to take control of this, you know, do what you need to do show something
Josh Moore: Whatever it takes to really keep us moving forward. So basically moving forward like Ola. This is talking about.
Josh Moore: That was the topics videos, um,
Josh Moore: So from my side. I'll just say I I've experienced more and more that recording things helps with the communication, especially with all the time zones, we're dealing with
Josh Moore: So that keeps me from needing to do the same presentation in the morning in the evening.
Josh Moore: And I know there's a Nepali meeting which takes place for the Pacific in California and time zones. Um, I'll probably never make it to that. But, you know,
Josh Moore: If I'm more than happy to send a video somewhere or you can send a video from some other time zone to this time zone. You know, it's kind of like
Josh Moore: A TARDIS of some form of sharing information. Basically, we need new ways of working. So if anyone has ideas you know we're open to
Josh Moore: Having everyone be involved, but having lots of meetings, obviously, is draining and time consuming. So what's the fine balance and what do you all want to see happen if you say everything should happen on GitHub. Then, you know, so be it. That's fine.
Josh Moore: Last point for me. Um, is there any feedback on how
Josh Moore: The setup of this meeting took place on image SC did it work for everyone, where the notifications annoying where they visible.
Josh Moore: Would you change anything.
Josh Moore: So the only so we did get the feedback this morning that having everyone say. Me too. Me too. Me too, me too.
Josh Moore: Was kind of annoying. So I'll try to come up with something that prevents that for next time the top level session. And here's where I need a yes or no or actually, I'll just say I'm going to do this, but you're welcome to veto it.
Josh Moore: Is to set up a group on image SC called N G, F, F, probably add all of you to it. And that way I don't have to add all of you to every thread, I can just add the group.
Josh Moore: If you don't want to be in the group you're welcome to leave the group yourself or you could tell me some form that I shouldn't do it. But it's gonna make my life simpler, so I'm looking forward to that.
Josh Moore: Cool.
Josh Moore: Five minutes left floor is open. I can stick around for a bit. It's good to see everyone
Josh Moore: Stay safe, healthy vote. I don't know.
Jason Swedlow: Just I'll just, I'll just follow up. I mean, I put some comments in the chat. Clearly we're going forward with this we have we have funding to do this and you know if if solutions exist. Tell us.
Jason Swedlow: You have specific requirements as we're discussing a few minutes ago around example metadata or whatever, say that as well. I mean,
Jason Swedlow: It sounds like. I mean, the convergence shushes GitHub issues, but also these forums or me Jesse, you know, pick your flavor.
Or
Jason Swedlow: And it's lovely to see you guys and see you all see everybody reasonably healthy so
Josh Moore: If someone adds a topic of a beer session for the next one, then we can
Josh Moore: We can make that happen.
Jason Swedlow: So it will become very popular.
Josh Moore: It's an official work event right i mean you have to be allowed.
Josh Moore: Cool. Then I mean, anyone who wants to disappear, feel free. I'm gonna hang out for a minute but. Take care everyone
Mark Kittisopikul: Thank you.
Ola Tarkowska: Hi.
Eric Perlman: Josh, I don't know how you managed to host two of these. And one day.
Eric Perlman: You have some superhumans guilds here.
Josh Moore: I am
Josh Moore: I don't think I really, I didn't prepare anything. So it's just kind of like, you know, I was kind of nervous, who is going to be absolute chaos, but everyone behaves so it's it's all fine, right, it could have been horrible, but it was it was lovely.
Josh Moore: It's good talking to people who haven't been to a conference in February, good priests.
Josh Moore: Are real conference.
Ulrike Boehm: But also common to Jason like thank you for putting together this paper about formats and repositories to kick this off because also this is super crucial because I think we need also their
Ulrike Boehm: guidelines and standards i don't know i i don't like to hear this word anymore. I have to say I used to so often already but but also with the repository part
Ulrike Boehm: I really do have to say that although there are lots of repositories out there for image data. I really have to say they still also try to find themselves. That sounds a little bit esoteric right now but
Ulrike Boehm: We had a talk at jamelia from someone who's also in charge of, I think, the image database.
Ulrike Boehm: And she was only saying they still don't know how much data, they actually want to put in these repositories and so on and so forth. So
Ulrike Boehm: If it's kind of only the data off the paper or everything. So this is also something where, where the entire community actually has to be
Ulrike Boehm: Involved, because I think decisions are being made. But I think when decisions are made, I think the people who have the data, who produce the data.
Ulrike Boehm: Should be part of these discussions and I mean I'm just which kind of supernatural right but I think sometimes people are over ambitious to get things done and then they sometimes might miss important
Ulrike Boehm: Important. And just as a
Jason Swedlow: Yes.
Jason Swedlow: Yes. Oh, I'll all correct and
Ulrike Boehm: Yeah.
Jason Swedlow: Yeah, that that whole side of things, the data repository data resource side of things is probably it's just probably the shortest thing to say is it's early days, and we're going to stumble for a while and
Jason Swedlow: I had right before locked out. I had the pleasure of having a drink with Helen Berman, who's been doing PDP for 50 years and, you know, she said, Yeah, you know,
Josh Moore: Should I, should I turn off the recording.
Probably
Josh Moore: Turning off the recording.
Jason Swedlow: Or live was yeah you know