Okay, perfect. Can you hear me? Yes. Okay, I cannot see my video, but I hope I appear normally. Yes, yes, you are there. Okay, good. Let me know if there are any strange things happening during the talk. Okay, but thank you very much for giving me this opportunity to talk about SAS 2. And apart from this data analysis part, which is central for SAS 2, I also want to talk a bit about what SAS 2 can do for you and what you can do for SAS 2. As you will learn, the SAS 2 is a community-driven project, so both actually input and output, I should say, is equally important. And so, sorry about that. Okay, so speaking about SAS 2, it's of course important to also mention the techniques that it's primarily been analyzing data from. So I actually plan to cover quite a few topics today, and I learned that's been particularly challenging for these presentations to find the right background. And so I arbitrarily choose some material that hopefully will cover the background of the audience as well. And I did it based on the, watching on the previous webinar. So of course, audience may change this time, but I hope that will provide you enough background to understand what SAS 2 is doing. But by no means I will be managed to cover everything. So I'm going to talk about the SAS, which is small-angle x-ray scattering, SAS, small-angle neutron scattering, and I will also mention a few concepts from data analysis. So let's move on. So SAS, small-angle scattering is the technique that is using either x-ray or neutron beam to investigate the sample. And the part of the beam is transmitted to the sample without any scattering and the part of it is scattered. And when we have the detector long enough, we can then observe the scattering pattern on the detector image. And that's usually measured in terms of the intensity in the function of the Q, which is the scattering vector, which is defined as the difference between the wave vector of the incident beam and the scatter beam. And using small-angle scattering, we can usually investigate the structure at the length scales from 1 to 100 nanometers, roughly. And because of this, we can learn particular information about the system. So we can learn something about the size of the particle, about the shape of the particle, as well as interparticle interactions. We cannot really get direct information about the atomic composition. That would be, to some extent, covered by the next speaker, Andrew Sazanov, talking next week when we will talk about the diffraction. Nevertheless, we can still gain quite a lot of information about the sample. And in some particular cases, when we have the sample, which we call that they are oriented or rented with respect to the incident beam, we can also learn and get information about the particular orientation. And we also can study magnetic properties of the sample. That's what can be done using small-angle neutron scattering. And the spectrum of the samples that can be studied using either sacks or sands is really, really fast. So essentially, it's only imagination that limits what can be studied using sacks or sands. So here is the list ordered alphabetically. Hopefully, you can find something for yourself. I hope your system is covered here. Most likely, it can be studied by sacks or sands. It's just only that I didn't put this on the list. Or someone else that I adopted the slide from, sure. So how sacks and sands are related. So the basic physics or the fundamental physics of sacks and sands don't really differ. But the properties differ really a great deal. So when we think of X-rays, they are essentially really available. And you can use the lab sources to investigate your structure using sacks. As for example, it's shown here, this nanobix device from the Regaku. That's essentially, as you can see, a small device that allows you for the studying nanoparticles using sacks. We can also go to the synchrotrons. And then we have much higher fluxes that allows for the more intense studies as well as the time resolution is improved. Which allows for the sub-milliseconds time result studies. Sample size, that's, there were in the previous webinars, there were questions about this. That's for the X-rays, that's essentially something bigger than 2.5 microlitres, depending also on the setup and the instrument. And that's considerably smaller than for neutrons. And speaking of neutrons, then we have to go to the large-scale facilities to perform neutron experiments. So here is the picture of Loki, which is the science instrument that it's currently under construction at the ESS. That will be for the science measurements. And essentially, as you can see there, that's something probably that would fit 100 of these nanopix devices inside this cabinet. And we of course have to go to the sources like explanation sources as ESS would be or reactor as, for example, ILL is at the moment. The one advantage of the using neutrons is that they don't cause radiation damage to the samples. Also provide to study time, perform studies in the time resolution. However, that's not exactly the same scale as for the X-rays. The sample required though is much larger. So we are talking here about the 100 of microlitres rather than 10s. On the other hand, it also provides something which is called contrast variation, which is the property of the neutrons that allows for the studying part of the complex. For example, if we have a protein nucleic acid complex, we can match out the nucleic acid and observe only protein or vice versa. Match out protein contribution and observe only nucleic acid. And neutrons also have spin. So as have nuclei, so when the neutrons interact with the nuclei, they give the magnetic moment. And by this, it's able to, and it's possible to study, study magnetic properties in solids, both static and dynamic. So neutron experiments usually have a higher entry barrier. So to say you have to sort of make a more justification for the, for the studying them, but it doesn't mean that it's not worth performing these experiments. And as I said, there are some experiments like contrast variation and magnetism that essentially can only be done using neutrons. But in general, these techniques are complementary. And speaking of the entry barrier, we hope that ESS will lower this and will allow more studies using neutrons. So what kind of information do we get in the majority of cases when we don't have magnetism or oriented systems, we usually get this 1D curve. So the detector image that I showed on the first slide can be usually averaged to this 1D, 1D scattering pattern that corresponds to the intensity defined in the function of the back of this scattering vector of Q. However, if we go for this oriented or magnetic systems, then we have something that refers to the 2D images and that's kind of data that we get. So, if we now think of what actually it's being covered by this data. So, this is the protein system that I have been working with at some point, it's called Modulene, which is the protein consisting of the two domains connected by the flexible linker. And we established that there are some confirmations that can be captured that the small angles scattering data corresponds to. But now if you think of the how much degrees of freedom or how or how many parameters you need to describe the systems both atoms and this movement is actually quite a lot. And here we have just the one single curve that corresponds to the system. So it is inevitable that we have a considerable loss of structure information by going from the sample to the curve that we usually have from the small angles scattering. And therefore it's extremely important to actually define your model correctly, also using knowledge from the other technique or physical principles or whatever else we know about the sample. As well as the risk to overfitting to data is quite high. Excuse me. So, for those of you who watched the webinar last week, maybe you recall that Thomas presented something like typical data analysis workflow. And so that's essentially something that we would routinely do for the for the analyzing small angles scattering data. And it works or it's the fundamentals for this are that we acquire the data and then we assume that we get this I of q curve for to the image. And then what we need to do we need to define model with the three parameters. And, and then calculate the scattering pattern for it and match it with the data. So, I will briefly go through the steps now. So the what I mean by the defining the model. So the, this is the probably the simplest equation that one can come up with in terms of the describing the I of q relationship with the structure properties. Of the models. The, the, or copying the models with the intensity so it essentially represents intensity in terms of the density of the particles concentration, something with is called form factor that corresponds to the particle shape and structure factor which corresponds to the particle interactions. And this form factors can be defined differently it can for example be calculated from the directly from the protein structure coordinates, as it's shown here in this example of timer. Or it can be calculated for the analytical model like for example the cylinder of the radius of 40 angstroms and the length of 200 angstroms. On the other hand, the, and then as tractor factor that that is defined differently and we have a different model so to say so for example here we look at something with is called hard sphere. And that's the model that corresponds to the exclusive volume repulsive interactions of the molecules. And the one thing to note here is that in this two cases above we have a maximum and this region we call low Q region, and here is actually opposite so couple this together. And if we have the, if we have them, for example repulsive interaction then we see the effect of this on our I of q curve. So, so this is particularly important when you study the concentrated samples, but in many cases, for example, in the, in the bio sector sense, people tend to dilute systems enough so as of q can be estimated to actually be close to one. So once we define this model, we can perform the bidding. So we let's assume that we have a data shown here and as a blue dots, and then we define the model the cylindrical model that is in this case of the land as it's shown here. And then for this initial step, we can calculate the property which is called chi square, which reflects the discrepancy between the points that we get from the experimental data and the and points calculated from the model. And this is divided by the error. And so this property is usually used for the optimization we are in this sense that we are minimizing this value in order to get fit. And once this is done, we can get the refined parameters and as shown here this data being corresponding to the cylinder model of the 440 radius and as you can see the drop in the chi square is going to struggle. So one thing to note here and if you recall what I said a few slides back I mean the risk of overfitting is high so one has to be careful in terms of just using the chi square optimization, especially in the system that involve a lot of degrees of freedom. So let's go back to the slides that I showed before and we'll now segue to SAS view because SAS view it actually covers all these three points from the model definition to fitting and producing the results and nice plots and whatsoever. Very briefly about the SAS view, SAS view originates from the National Science Foundation founded project called dance that was initiated in 2006. And it continued like this for the few years and then in 2013 it was turned into a community driven project. It's currently supported by nine facilities both x-ray and neutrons. We have about 40 contributors, maybe even more. About 15 are active at any one time. And we have a steering body consisting of pole battler from NIST, Matthew Ducey, O'Rannell, and the Jackson ESS and Steve King Isis. And the most coordination of the project is actually done through the bi-weekly calls when we talk together and decide what we do and what we not do and have fun as well during these calls. So that's really lively collaboration and nicely going forward. And we also have regular camps and other events that I will mention later on. And most importantly, some of the SAS view members are on this call, so I am at least aware of the pole battler Steve King and Nicolas Martinez that said that they will join this call and they can also participate in the discussion if I need basically a backup on some questions. Because that's really one of the strengths of the SAS view, that we're coming from the different fields of the expertise and we work together in this interdisciplinary environment and I hope we are producing a good piece of software. So this is how does it look when it comes to program and that's how actually our day-to-day work looks like. So I think that there is a typical understanding of the SAS view as being a primary coding project, but I would say coding is just a part of it. I mean the results of the part that involves working on the theory all start regarding the maintaining the infrastructure project management documentation and tutorials are actually equally important as all the other parts and educational outreach is also important as that we try to perform. So coding is not only part of the SAS view project. So now let's dive into the SAS view. So this how SAS view looks like when you open it, at least on the Mac OS X, and then you can see that you have some load button and send to the fitting. And I will go through some of these functionalities. Now, so this is how the typical fitting looks like. So as you see, it's become a little bit more easy. So I will go, I will try to go step by step for these different functionalities. So first of all, we can load the data and we have a data management table that allows for the loading common data formats, including an ex-cancer format as well. And then we can what we call send our data to different analysis so one can choose between fitting P of R inversion correlation functions and invariant calculation. One can also manipulate plotting to some extent in this in this field. And then speaking of these models, I mean the model definition. So what I what I presented before was, for example, the cylinder model, which is one of the 70 models of the form factors, or even more than 70 models of the form factors that we support in the in the SAS view, so they can be choose from this different menu from the categories and modeling as and the same is true for the structure factor, which can be coupled with the form factor. Then we can define something we just called polydispersity. So in the real life, we usually don't have samples or the particles in the sample that look exactly the same, but they may differ slightly in the overall shape. And therefore, we may want to introduce the polydispersity of the data and SAS also allows for this. The same is with the resolution smearing that's more related to the to the fact that how the experiments was performed and the instrumental setup. And SAS provides the two ways of actually defining either manually or automatically from the from the file if this is of course written to the file. And when it comes to the feeding modes, we can actually perform either single feeding with the just the one curve as it's shown here. But we can also do the do the batch feeding, which means that we can apply the same and feeding of the same model to the multiple datasets, as well as we can perform simultaneous feeding, which is the feeding that involves using the common parameters across different models for the for the for the multiple datasets. And I also mentioned that we can perform this to the analysis and in a SAS with the formulation from for this is done with the something with this called orientation of polydispersity. And it's, it's been set up in a way that it decouples the frame of the orientation from the from the form factors of to say, and the, and therefore it can be also performed efficiently. And as a matter of fact, this, this computations are quite computationally intense. And therefore, we particle are for this models, but not only for this but also for others enable computation on the graphical processor units, this graphic cards, and then allow for the fast execution of the feeding. The other feature of SAS view is that it can use something which is called CSAN's data with the spin equals small angle neutrons category. And that's very interesting and technique that's using polarized neutrons to actually extend the sort of the this limit of the of the landscape that can be pro by by some so here we are talking about the range from the 20 nanometers to 20 micrometers. And SAS views set it up in the way in such it set up in the way that it can actually use the full potential of the form factors that that that we have readily available and there is a trick mathematical trick called uncle transform then allows transformation of this models into the CSAN's data. And it's, I'm, I'm not going very much into the details about this technique, but if you are interested, then I would, I would refer to the papers of the Dean Bowman, who been also contributing to to SAS view on this project. And the, as I mentioned them. And the sort of core of the optimization is, is driving the way that the feeding is performed in SAS so it's very important functionality and actually for SAS we benefit a lot from the project called bumps, which is developed by Paul Kinzo from this. And it allows both conventional and based on optimization, which provides uncertainty estimation of the input parameters and that's very important in in terms of the small angle scattering because you actually, as I, as I pointed out that the loss of information it's it's considerable. And therefore we usually have the quite considerable error bars and therefore we also want to know how this uncertainty uncertainty is reflected on our fit. So bumps allows this kind of analysis as they are shown here at the different plots and the trajectories as well as uncertainties, as well as provides quite some choice of the of the optimizers. One other nice feature of SAS view that I think it's a particle and useful for the, for the community is the fact that it allows for the easy addition of the packing models. So if you have the system that you cannot really choose this any analytical model from the 70 plus models that we have in the SAS view, then you can write your own. And that's actually this task can actually be done in both ways. So one can start writing up directly from the Python and then looking at that, usually looking at how other models are structured, but we also provide the tool that the model editor. And that allows in the few simple steps to generate the Python code that can be then used in such and that's actually directly available in such and you can use it straight off. Once you click apply button on this model editor. And if you then have some complicated model and then actually requires more speed optimization than usually in the recommended way is to go for the for the C implementation that is also nicely interface to Python that we support so it's actually can and so says we can support two types of model and model files and and performance and optimization on the GPU. It then also ready and the and the feature of the models that at least from the from the SAS view and models that we support we provide is that we, and that we always have a full description of what's happening in the in the model so it's easy to keep track on what exactly the math is that we like to perform. And we also test our models so we check in the every time we add a new feature to the code that actually the model keep the same answer as we would expect. Okay, so I've been now discussing mostly things that and then assume that you know the model but that's not essentially not always the case. Sometimes we, especially at the initial stage of the analysis want to do something directly from the data. And this can be done through, for example, calculation of this poorer that scattering invariant, which is essentially integral that it's proportional to the fluctuation of the scattering of the face composition. And what it actually provides it provides the independent estimate of the volume fraction that then can be used to to understand porosity of the material. And surface area, which can, for example, corresponds to reactivity. It can also be used as a sanity check if you want to sort of see if the same sample gives the same answer of the different instruments. The other possibility is to use the P of R and the per distance distribution inversion. And this is probability of finding a vector of land are between scattering centers. And in SAS we use this P of R formula with this using Morse derivation. And what P of R provides it can provide the information of the, on the maximum dimension of the of the molecule. But as you can see here, I mean, depending on the shape of the particle. We also get the concern of different P of R functions. And therefore we can learn something about the our system, even without introducing the model so this can be done directly from the data you can calculate this property using Fourier transform, or inverse Fourier from scattering data. And in SAS this can be done also through this what we call this perspective. And the, and this, there is a part from the, from the, from the fit P of R fit that we can generate. We can also use the exploratory tool which shows us where this D max should be sort of defined because there are some parameters that one can have to set up in this analysis and SAS is providing some nice features to explore this values. The last sort of core functionality, as I would say, in SAS is something that is particularly useful for the material science and that's the correlation functions that can be interpreted as a imaginary rod moving for the structure of the material. And SAS provides the different correlation functions one and three dimensional correlation functions that can give us information about the periodicity or, for example, if material is amorphous. So, so far I've been discussing this analysis or the perspective functionality of SAS view. However, that's not all actually that the number of tools of the future is actually much larger. And just to mention the few we have tools for the scattering and density calculator, slit size calculator, generic scattering calculator, for example, to calculate the, and the scattering pattern from the, from the protein coordinates. And, and also a few other utility tools. So I'm not for the interest of time I'm not going to get into these details but if you're interested please check either in SAS view or other resources. So very briefly about the SAS architecture, how is it structure and what one can do. So the part that I was talking about that was the sort of outer layer of SAS view, which is this graphical user interface and that's what we as a, as a user scan interface with that with the program without touching any code. However, these days it's becoming more and more increasingly popular to use the Jupyter notebooks and other scripts to to run the software. And actually, SAS view also provides them means to do to use this kind of interface. So we have something which is called SAS calc, which is essentially the backend calculator for the graphical user interface. We have this package which is called SAS models, which is defining both form and structure factors. And we have this thing called bumps, which is the optimizer. And because of this, we can, as I said, run SAS view from the script. So here is the example of the feeding using SAS models and pumps. So I'm not really touching the outer layer at all. And once this is done, one can detach the or the deploy the script on the on the computer class and rabbit run it over there. The other possibility that we also been working on, I mean, though it's still a little bit experimental is to define all your parameters inside the SAS view and your feet, save the state to touch from the GUI and then run this sort of project file on the on the cluster. So that's also the need functionality that doesn't require any knowledge of the scripting. However, it opens up for this possibilities of using computer cluster if you have a long analysis. This is just to illustrate the another example using the scripting interface. So we can also use this for the for the bird distance distributions calculations as well as we can just use the SAS models directly to generate our favorite form factor or whatever. So this is this is essentially covering most of the of the SAS view. In terms of the functionality, what I would like to briefly talk about is how to use SAS and what resources are provided. So this is typically the how you start using it you go to the to the SAS view website and then you choose the choose the downloadable version, and then you start interacting with this as you probably notice, I mean, we currently support version four and version five. And version five recently is being getting more and more attention so there are more frequent release. And that's something that will eventually move on, but there are still user users that prefer use version four so we still support it. If you don't like good at all, no matter if four or five, then you're of course very welcome to clone the repository and get an interactive code code is written mostly Python, plus some C part that it's used for the for the GPU optimization. But you're also welcome to do so. And so I mentioned that the five version is being released more often, often these days, and we mostly been releasing the point releases that will be by point me release I mean the 502. There is actually 503 coming up soon as well, that we've been fixing many bugs, but also providing the new features and improvements, mostly driven by the user requests. So if you want to get some feature done, and I think that the best and some feature done sooner than later than, then you're of course welcome to to talk about this and or report it to the different things that I will just discuss on the next slide. And for the sort of bigger picture we have something. We have a SAS view roadmap which is the living document that we keep in the five years span and that defines more top level goals for SAS view. And here are examples of them. Of the what we've been planning for the for this coming year essentially. So as I said, we, we plan to release a bigger version and and complete some, some other milestones. So if you're interested, then please take a look on the on this link below. However, if you, as I said, encounter some issue and you want to share it with the community, you of course are welcome to email us. But also, we store everything on the GitHub so there are no secrets, everyone can see what we currently been working on. So day to day issues are stored on GitHub and are available. If you're interested in this, then please take a look on this. And I would also like to mention what says you cannot do and it has to be for about it. So we are not saving the word here. And so we don't do molecular modeling and as well as ab initio modeling. So there are, I just mentioning to software packages here. So SAS see that's been doing molecular dynamics and combining this with a small angle scattering. So if you are interested in this kind of studies then I would refer to to these approaches. And if, especially if you are coming from the bio sun sucks or suns community, you most likely encounter software called at SAS, which is really comprehensive toolbox that is also providing many other functionalities like this ab initio reconstruction that I would advise to use with caution. But that's, that's not really functionality that we that we cover with SAS so as the other rigid body modeling using the protein models. That's to some extent true with this with this molecular modeling because I also I will now demonstrate on the example that I worked. And that now with this with this possibility of using SAS from script we can actually achieve many of this functionality as well. So this is the example of the virus capsid assembly. So the, the, the project that I've been working on at the Lund University. And the basic idea of this project is that we have a self assembling virus capsid so these are proteins that assemble to the, to the final product this wall called capsid. And typically what we don't know is what happens in between. And if you think in terms of the number of combinations that you can have as for example this capsid concept of 240 subunits, then you have a really humongous number of the combinations that you can go through one state from this from this start state to the end state. And we combine molecular modelings with this with the small angle x-ray scattering and collected the data at the ESRF last year that was done in the collaboration with my colleagues from the different institutions and for the trained eyes you can see that for the, for the later time point for the trained small angle scattering eyes I should say you can see that you have a portion like structure coming up at the later stage. So long story short we established that the disassembly pathway proceeds truly essentially to intermediates so we have a dimer state at the beginning, then we have a hexamer they are not exactly on the same scale. But then we have the, then we have the intermediate that corresponds to the 80 subunits and then at the end we have a mixture of the different capsids and then using the some clever mathematics we established that and that we have a, we can infer the population weights along this time. That's an exciting study but the mostly the reason why I brought it up is that at the beginning of the studies we didn't really know what is the exact composition of the end state and we've been getting information from the electron microscopy that it's, that there are, it's mostly dominated by this bigger capsid. I consider the 240 subunits and what I did, I combined this atomistic model together with the SASV analytical model in order to learn what, what are the fractions, what are the parameters of the potentially the other models and based on this we established that we can actually, or that we have the mixture of the, of the different capsid which is smaller than the, than the one that we are getting an electron microscopy data for. So that helped out with the initial analysis to, to establish this fact that it's consistent in this data. So just very briefly finishing off because I'm running out of time and we provide a lot of resources for the education and outreach. And so we have a, of course, website documentation, different tutorials, we've been teaching different schools and giving different courses. We also have a eLearning platform. So the, differently, we, the SASV course is also ported on the, is available from the enutrons.org which is a eLearning platform. And we also have some other communication channels. So please check them if you're interested in them. The two aspects that I want to mention are the one is Marketplace, which is available at this URL. And that's actually very nice venue for the, for the community contributor model. So if you develop the model that you want to share with the rest of the SASV community, then you can upload it over there. And that would be available and one can use it for the, together with SASV in the different, in the different aspects. And, and that was actually work done by the ISIS summer students to be the archcruel who did an excellent job on setting this up. And that's really a nice tool for the community. And I mentioned this cold camps or solitary camps and other events. So we are planning to provide more training. So we have a sort of long-standing goal for this, but we want to have a, have a boot camp, which would provide the training from the basic use to becoming essentially a core developer. One can stop at any, any, any stage one wants. And we also, and if you're interested, then there is a link to Syllabus here, what we're planning to do. There is no dead state for this, but we will announce for this as also for the other events, all the relevant information and these different channels. And, and we also recently been having hackathons because we have to move our regular events to the, to the virtual events, but I think it's been working quite fine actually. And we, and we are still hoping to have a cold camp 10 at some point soon. That was planned originally for the April this year, but it was canceled for the obvious reason. And then most likely will be held at Caltech at some point. But as I said, I mean, please follow this, this communication channels if you are interested. So lastly, I just want to say that you are very welcome to come and work with us. We have a lot of fun together. We don't only do the coding theory, cracking and math calculation. We also enjoy a simple pleasure of life and like eating and stuff. And with this, I would like to thank you for listening and I'll be happy to take any questions now. Thank you very much. My take was a very interesting talk. So we have several questions for you. Hope you're ready. So we start with a short question from one of the attendance. So does the form factor also includes the size? That's a very short and general question. Let me open the chat. I want. Okay. I will also just try to read. So it's like, so do I understand that the form factor also includes size? That's the question. Right. So, okay. So I was trying to just also follow this. So sorry about that. No, it's not the difficult question. And so yes, in this sense that you, when you define the form factor, then you account for the size and shape of the particle. Okay, so we continue with other questions. So can we calculate the pore size and shape of a pore material or only it can be measured for single crystal using stocks? So both stocks and science can be applied to the porous materials. So that's not, that's definitely possible. Okay. The next question is, Susview, could find application in organic thin film applications? Can you repeat this? I mean, there is something with the noise. Therefore, I've been trying to find the chat. Yeah, you could build our microphone. So Susview could find application in inorganic thin films. Inorganic films. Inorganic thin films applications. Well, I mean, I personally don't have any experience with this systems and I couldn't recall any paper doing this. But maybe my Susview colleagues can comment on this. Paul, Steve, Nikola. We can unmute them if we find them. So Paul is with us today, Paul Butler. Yes. If they want, of course, other than that, I would say that it's most likely yes, but I just don't know. So let's welcome Paul here. He may still... On the audio. On the audio. But you might not be... Okay, we keep... Okay, Paul, you need to unmute yourself. Good. Welcome. So nice to have you with us. Are you in the US? Yes, I am in the US. I did not fly over for this. Okay. You're welcome. The answer I'm trying to think on thin films. If you can model it, then SAS view would be used for it. I try to think of thin film applications. Mostly what I know people do with that would be usually looking for domains, maybe, in thin films. In which case, definitely, you could use models to try to understand perhaps the size of the domains. If you are looking at texture, then you might be using the invariance to look for the interfaces. So yes, if you can do small-angle scattering with it, then you can look at that data with SAS view, essentially. Great. We keep receiving more questions and more detailed questions. So when Paul turned up online, people started to get more curious. The person in the audience is asking, I encountered some misbehaving when activating polydispersity. I will try the latest version first to see if bugs are solved. But can you comment which procedure is expected to communicate with the developers when encountering some issues? Yes, thank you for this feedback. We are aware of the problems with polydispersity, especially for the previous versions of SAS view. If you are using SAS view 5, because I presume that's the one I think for the SAS view 4 there shouldn't be. So if it hasn't been solved with the 502 version, then hopefully it will be solved with the 503, because we have also been addressing polydispersity issues over there. So I would recommend checking out one that will be out soon, hopefully. But the way to interact, the most straightforward way is to drop us a line and write an email. And the email for this, it can be found on the website or in this presentation. And the other possibility, if someone has the GitHub account, one can also create an issue directly. And by going to the interface and then writing, I discovered this and that and so on. And also the GitHub may help out actually recognizing that if this is common issue and actually we've been already working on this. So that also may give you a hint that okay, they already know about this and they are working about it to resolve this. Great. So we want to remind the audience that I can always send you questions. Yes. Can I add one thing for one second? On the polydispersity question, we know actually it's not fixed in 5.0.2 completely, we know that. Nikola, who from ILL has been working on that hackathon. And I believe, having looked at it, that it will fix everything that we now know about. So if you wait for 5.0.3, which should be out in a few weeks, I hope. If you still find problems, then either send a note to developers at sasview.org or on GitHub. That's great. So yeah, the audience acknowledge you for the very detailed answer. We have another question. Does sasview provide solutions for size, spacing, correlation, approximation for dense packed particles with certain size distribution or polydispersed orientation in loosely packed system with unique shaped particles? It's a lot of questions I can repeat. Sounds like very specific, domain specific question. I would say that probably would require... So we can provide what we can provide and we do our best in providing this. We cannot support all the models possible. So to be honest, I don't know exactly if we have a structure factors to model these interactions. But the other part of answer is that nothing prevents from writing it. Hopefully the mathematics formulation is done then and can be done through the plug-in model system. Yes, exactly because we want to remind to the audience that I can always find all the speakers information online on the links web page. So they can always contact you, the developers and then maybe ask and interact with you because you're very kind and so available. So we really, yeah, thank you for this availability. We continue with the questions and those are more general, I would say. So can we use sasview for 3D topography? Not that I know. Maybe in some aspects. Yeah, simply I don't know. I wouldn't say directly but there might be some aspect that will be complementary to the other software. Then there is another general question. Any preliminary characterization tool before we use sacks or sensors. So because you have been talking about your data with certain parameters. So before going actually to the real experiments can be done before home. Yes, of course, especially if you measure at the large capabilities, it's very important that you have a sample that it will behave and you can perform the measurements. And you can come back home with the good quality data. So I personally have experience with the biomolecules. So I mean the anything that can tell you about the concentrations and the oligomeric states that usually useful like AUC. For example, I don't really know how about the other materials, what what can be applied. But I usually the if you have a monodisperse sample, especially for the for the biosystem that that usually helps a lot. And for this I would advise for the following the instrument specific documentation. Usually they provide the hints what what you what you should expect or the or the or what are the sort of the checklist that you should do. Before going there just not to come out disappointed. I mean, we can do our best, but the data has to be good enough. I mean, the information lost is considerable. So we already working with the difficult problem. So any other factors that it's differing the data is of course just making problem more difficult to solve. Yeah, but it's really interesting to see that people can actually be introduced to the software that will be used for the data analysis. And then when you know what are the critical parameters and focus on them and get information about that before going. It's really important. So we continue with another a little bit more specific. So how do we calculate the surface per volume ratio from scattering vector? Sounds like an invariant question. Maybe Paul can take it because he recently been cracking the match to the to the death for this. So I think you are the expert on this now. But you can maybe keep it keep it general and maybe people are really interested. So I think the the best answer that I can give. I mean, if once the this 503 version is out, Paul did an excellent job on putting the commendation for this. And the everything is very nicely written over there. So I would say that for the particular equation that I would recommend getting this. And the yes, because otherwise I'm not sure how I can go over the map simply, but of course. No, the math is complicated. You don't want to look at that. Basically, it's very simple. If you're wanting to look at the surface to volume ratio, what you're really looking at is the interfaces. So you want very good data at high Q. That's where you're going to get all the interfaces will show up. So if you know the porode constant, which you can basically that's where you get the extrapolation high Q. So you want good data at high Q. And then just plug in those numbers into the invariant calculator and you will get the surface to volume ratio. So you want mathematical details, you can read it more carefully. Very nice answer. Thank you very much, Paul. And we have the last question then. So can we estimate that the assembly. The state of micromolecule system in solution. So. The question is using science or the other methods. So I mean the. Yes. And the answer is generally yes. So I mean, that of course it's sometimes tricky because you can have the convoluted signal. So essentially if you have a mixture of the different oligomeric states, then what you see from the scattering does the mixture of this. So we don't see this for particular species. So you have to the convoluted signal and there are different tools to do this. I mean the SVD is the singular value. The composition is one tool. And there are also the potentially better approach using, for example, MCR analysis, not getting into the details. But one can also do some other decomposition and I've been developing for this time result. The system, the capsaid assembly, I've been developing the basin approach to decompose the system. So. Currently from SAS, it's not directly available. Combined together, this can be done as I demonstrated in the example that I showed. So in general from data, yes, from SAS view, not at the moment. Okay, so thank you very much.


Welcome everyone. This is Melissa Armo with the Stock Swoosh. I'm reviewing the options for the calendar year for 2016 and the reason is I wanted to see the best trade of the year, the worst trade of the year, are the worst call I made for the year and the best call I made for the year. As it turns out, Facebook was the worst call I made for the year in the first trade that I called and yet it ended up going where I predicted it would and through the strike originally. But let's just go back to the call because I I ended up taking this position and I also killed it with a half loss, which which is a rule now that I have decided to implement for all options trades. And actually, it's a really good rule because most of the trades I've called in 2016 for options have gone immediately into the money. Whether they were a 50% return investment or 100% return investment or 300% return investment in the first 24 hours or 48 hours, I've realized now that my ability to be able to call these to go immediately profitable is a high and therefore if they don't, something's wrong and it's a sign. Now, when did I call this? August 1st, there's there's a lot to be learned from this. It didn't work and I'm going to show you why. August 1st, I called this. I said FB strike calls 130, expiring August 19th. I didn't I didn't leave it till here, but I just want to show you. It did not get through that number. So after I called the train here at the stock dipped, the price of the option dropped since I bought it, it rallied back. I think it was profitable for like a little bit of one of the days in here, like a few hours. Like if you literally you could have gotten out of there with a couple hundred bucks and if you didn't, it didn't ever win anywhere. It dropped and dipped. I killed this the day I took the Baba. What was the day that I took the Baba? Because I just dumped it, the 11th. So I took it on the 1st and I just killed it. I kept it the day of the 11th and then I threw the rest of the position that I had because I didn't lose in it in entirety. Again, I lost half and I killed the rest of it and threw the money into the Baba. That was a really great decision. It was I didn't even think through the decision. I was like screw this thing. Baba is really good. I dumped it. And I don't really like to have two options trades on while I'm also day trading. I just think it's too much in my monitor. But anyways, make a long story short. I just threw it out. I dumped it. It was a great decision. The trade didn't go into work. But I will tell you that after the expiration of stock rallying blew up, blew over the number, blew over 130, ran up to 132. I did call a second trade in Facebook after I saw it would blow over the high of this gap up that happened in the earnings that fail, but still continued hired and made a new brand new autumn high on the stay in the continued hire. I saw it would do it, but I didn't do the second trade. I was in the Baba at that time. And so I didn't do it. But the second one works. If you lost in the first one, he made one in the second one. But worst call of the year was this because it didn't go anywhere. It was never really up any amount of money that you could say, I want to take this out, which would be 50 percent, 100 percent. I know they sound like crazy numbers, people. But honestly, the option calls that I've made for this calendar year have been so incredibly profitable that people's expectations now that are signed up for the letter are very high. Someone could take a trade and risk a thousand bucks and be up 250 dollars, which is real money if that's 25 percent, you know, on the amount you risk and not get out because people's expectations now are that they're going to risk a thousand dollars and make a thousand dollars or way, way more. So I've kind of set the bar really high for myself for 2017. I'm OK with that. But I will tell you that this was the worst call I made this year. It continue. The second trade worked. I didn't do it. And what what did I learn from this? What did I learn from this that I can take into the future? And actually, I've learned for future calls I made because this was a couple months ago after a stock gaps up on the earnings and fails. I didn't day trade this at all. I don't short bullish gap ups, certainly not ones to brandy well to my eyes. But I saw it would hit the 130. How long did it take? It took a little bit more than a month. Took about five weeks to get over that high. But what I learned from that is that the stock has to digest the sell off. And that's what I that's a mistake I made. I immediately thought it would full on rally back and go over the selling here because the stock was still strong and I was right. I was right. It did what I wanted it to do. But I didn't get the timing right. And with options, you have to.  And that I'm very, very good at that. But but this I was so certain it would go to 130. But it had to digest the sell off from the gap up on the earnings that failed. And I just, you know, never again will I do this until after the digestion is clear. So the digestion happened. It took it took a couple of weeks and by the time the breakout bar happened here, you knew it was going to follow through, which it did. It didn't have much of a follow through, but you still would have made money going along here here. But it was a quick trade later, which I called and people made money in. But I didn't do that one. I did this one and I killed it with a half loss.  It needs time to digest the move and no one can predict that. So you wait and you don't take a trade until it happens. So I learned a lot from this and I won't make a mistake again about this. And I have not called a trade like this since then. But this was the worst call I made in the options letter for 2016. I did not take a full loss. It took a half loss. I threw the money into Bama and it worked out good for me. Good review of the options trades for 2016. If you'd like to sign up for the options letter for 2017, email me at Melissa, the stockswish.com. I have a sale going on to the end of the year. And, you know, I think for those of you that have been looking and trying to find a way to actually sign up for the class or save money for the class or don't people who do not have money for a full on day trading account, the options letter is something that you could do. You just get the trade calls and you can you can risk as little as much as money as you want in them. And you don't have to have a day trading account to do so. Email me with Melissa at the stockswish.com for more information. If you want to sign up for the letter, I think it's going to be a good year. I've reviewed the mistakes I made like this one here for 2016, for 2017 to make better calls. I've also reviewed the very good calls I've made this year, which Bama was, like I said, the top one. And I think in next year's calendar year, I'm going to risk more in the ones that I have 100% conviction in like Bama. And I will stay away from these that collapse into the earnings. It's just it's not that the stock won't get over the high it did. It absolutely 100% did, but no one can predict the timing. And the one thing about options trades you got to get right is A, you got to get the direction right and B, you got to get the timing. Thanks everyone. Have a great day. Email me at Melissa at the stockswish.com for more information.


Alright, so this is Omri Misgav and he is going to talk about running root kits like a nation state hacker. Hi everyone. Good morning. As I was introduced, my name is Omri. I work at Fortinet in Israel. Most of my work is around OS security and OS internals. Today I'm going to talk a bit about driver signing enforcement. And basically how it works, how it works, the internals of it, how attackers abuse it, what Microsoft tried to do in order to prevent it. And then we'll talk about some new tradecraft. Hopefully that we'll also run some live demos and everything will go as planned. So what is DST? Basically there is a feature in Windows that is called code integrity. It is used for threat protection. Basically it's used to sign code and some aspects of it means that in order to sign, in order to run drivers in the kernel now you have to sign them, to digitally sign them. And every time you want to execute a driver, basically the operating system will check its signature, will verify it and by that we can improve the security of the OS. We can know from where drivers originated, who are the authors and if we trust them and make sure that they are not modified on the way sometime after they were built. Moreover, the signing is not something that just everybody can do. You used to need a specific code signing certificate that came only from a handful of approved sources. And over the years there was another limitation that was added by Microsoft that you had to give them your driver for them to sign it. And without their signature it won't work. You won't be able to run it. Which if you think about it for attackers is not really ideal. You just hand over your payload to the defenders. It's not really a place you want to be in. So how does it work in practice? Basically when the system boots up, if you can see the call stuck on the left, at a certain point the kernel will mark the CI enabled flag as set to true. And it will call another library in the kernel that is called CIDLL. And it will give this initialization function that is exported by the DLL. It will give it a callback structure that the DLL itself will fill with callbacks for the kernel to use later on. And the DLL will also set its internal state to be set as on. Next up when a driver will be loaded you can see the call stuck on the middle. Basically when it's going to be mapped into memory the couple of wrapper functions that will be called. Basically those are just very simple wrappers for the callbacks that CIDLL provides. And what they do we can see on the right, on the right side on the disassembly. Basically they check the flags, they check the global flags to see if the code integrity is enabled. And then they just check that the callback is valid, that it's not a null pointer. And that's pretty much it. Both functions, both callbacks that will be called is the validate image header and validate image data. And that's pretty much how it works. There have been a few changes along the years. What I just described was mainly for Windows 7. The changes are really, really small. So from Windows 8 basically the enable flag was removed. So right now the state of the driver signing enforcement is only set in the CIDLL. And there are more callbacks that CIDLL now provides but they are not really important for our case. And because there are more callbacks that are used then some offsets in the structure change basically from Windows 8 till today there wasn't any critical change for us. One other thing that is important here is that basically right now there is only a single function that will be called, a single callback that will be called when the driver will be loaded. So how it's been abused in the wild? Basically we go, we or mainly attackers go in order to load their driver which is usually unsigned or untrusted and they just go and flip the bits of the flag depends on the operating system build.  The way it's being done is that all of those variables, all of those callbacks are basically internal structures, they are private, they are not exported in any way but they can be easily found with the simple pattern matching. Again with barely any change between all the Windows builds and in order to be able to write to the kernel basically they bring their own driver or bring their own vulnerable driver and they just leverage it in order to gain right permissions to the kernel. It has a lot of pros to it because it means that we can just reuse this capability no matter when we want to. So a few steps that Microsoft tried to implement in order to fight this thing is basically it's first apply patch guard to it from Windows 8 and Windows 8.1 there were improvements. Now they try to block attackers from gaining the right primitive basically they deploy driver block lists which is effective but there is a problem with it because it doesn't cover what we don't know if we find a new driver that is vulnerable, if the attackers find it so they can use it and everything will just go on. And the major change that they tried to introduce with Windows 11 was basically using KDP, kernel data protection, it's a new feature based on VBS architecture basically leverages the hypervisor in order to enforce read only permissions on specific pages and they let drivers, other drivers use it as well and all other kernel components and that's pretty much what they did with Windows 11. Now CIDLL was tweaked a bit. Basically we can see that CI options is now being provided as a parameter to the KDP API and the global variable was moved to its own page which is called now CI policy. It's like a unique section in the P that it's found in. So just to recap for a second before we get into the new stuff basically how the DSC tampering works is we locate something that we need to change then we overwrite it, we load the driver and revert back. We're going to focus on the first two points here with our main goal is basically be able to change some data and not touch any code pages or modify any executable pages whatsoever. The first technique, it has a very creative name for it it's called page swapping. Basically because the protected page we cannot write to it because there is another set of permissions that is being enforced on in the slot PTE. Basically we can try to it no matter what we'll do. We can see the illustration here of the mapping but still KDP doesn't really enforce the way that the virtual memory is being mapped to the physical memory at the end. It tried to do something like patch guard that it goes on periodically and tried to verify it but since it's periodically we can still make some short-lived changes. Instead we're going to create our own page, our own copy of the page and we'll make it writable so we can set whatever value we want to it and then we'll set DSC as off in this page and then we just need to somehow make the same virtual address for the original variable to change its value to it. For that we just need to change the page table and basically we only write the address of the PTE, the PFN there and then the next time the virtual address will be used it will go to the page that we control and set the value. So just to go through the steps by steps here we allocate a new page, the page we allocate is in the kernel we need to find the CI options flags just as it's currently done in the wild there's nothing new about it here. We need to read the PTE base, just a short explanation on this basically the page tables are also found in the virtual address space in the kernel with simple bitwise calculation we can basically convert the virtual address that we want to access and find it's matching PTE for it. There is a problem with it, basically the address space is now randomized but it's a very good thing that I already had some research in the past that covered it so we can just read the new PTE base with a single read from kernel using an exported function in Ntos as we can see here then we go on and read the PTEs that we need to change the PTE for the original page and the PTE for the page we allocated then we need to copy the page because if we're going to swap the page in order for anything else not to break we need to copy the entire values there because we don't really know what other things are in the page itself the flag itself is only 4 bytes, page size is 4 kilobyte we need to modify the value in order to set it to turn it off and then basically just switch the PFS as we showed earlier load the driver and restore the PTE so this is pretty complicated when I walked on it I wasn't really happy so I tried to figure out some other way to solve it and make it a bit more feasible to use and with a few very slight changes it's very easy to do basically instead of allocating a page in kernel we're going to allocate a page in user space and then everything we need to locate just remains the same instead of copying the page and doing a lot of kernel reads we can just, in the case of CIDLL since the variable was moved to its own unique page we can just use the default values for this page most of them are just zeros and just set the value that we need for the flag and then again change the PFN load the driver and restore it so demo time I have a Windows 11 build here an inside preview build from like two weeks ago we'll boot up in a second the first thing we're going to show you is that we see the build number and we'll see that VBS is running but the only thing that is being enabled is credential guard KDP doesn't appear here for some reason so the first thing we're going to show is basically that the current technique in the wild doesn't work so here we're going to expect a blue screen yay, we can see that it's blocked on the right and let's see back, second okay, so now I have my rootkit over here and just show you that it's unsigned and we're going to quickly install it we'll try and run it and see it doesn't run we get an error we'll run the page swapping and now it runs you can see the output here you can see print by the rootkit itself and I stopped it and now we'll try to run it again and get an error okay so this is the first technique it's pretty complicated to implement it involves both reads and writes to the kernel and we wanted to find a different method to do it that won't be as complicated as that so we found another way if we look basically on how the callbacks work so there is some address that basically calls CI DLL and this callback needs to return as 0 okay, sorry it needs to return 0 and now instead of just calling to the entry point of the function maybe we can just replace this functionality and get some other way to return 0 and then it will just work as the same the authorization of the driver will work so we're basically going to swap the callbacks but we need to find out how to do it so first we need to find the global callback structure it's very easy to do because CI Initialize is imported by the kernel so we can just find a reference and import address table for it from there we need to go back and find the register assignment for it and basically when we do we see that the address will point to initialize to uninitialized memory in the data section now we need to find a new replacement callback which is pretty easy to do because all we need to return is 0 there are exported functions in the kernel for this and if we don't want to go that far we can just use the IDLL itself and look for gadgets or exported functions in it now we need to find the way to restore the original callbacks that's important so we can just do this entire technique without any kernel reads so the pattern that is used to initialize the callback structure is pretty much the same in every build so we can just look for it and then we get a list of addresses that we need to actually verify that they are functions so we can basically traverse the exception directory and look for entries that are basically function start addresses and then we know that we got to the right place so then we need to set the callback which is pretty easy load the driver and restore the callbacks again go back for a quick demo so right now I disabled DC and then we see that our rootkit is back running after we didn't manage to run it we re-enable DC sorry I can't see it so it's stopped as we can see now and we can run it again so I'm a bit out of time so I'll try to go quickly about these two next slides we can see that basically we managed to find some managed to find a new technique that is pretty synonymous to the existing one in the wild there is a way to mitigate it basically what we suggest is like try and find all of these internal states internal variables ourselves just as attackers do there is no reason not to do it it was proven as stable till now at least we can copy the state of the variables and then just re-test them again and again every time a driver is loaded it's also easy to prevent because once we see that there is a change in the variables we can either block the IO operation or just restore the variables to the original state and let the operating system do the work for us and just to sum it up basically DC tampering is still feasible even with everything Microsoft attempted to do here doing like providing data oriented mitigations are pretty difficult as you can see the real solution for it at the end is called HVCI it's another feature that Microsoft provided on top of VBS it's a very old feature it's like there from the beginning pretty much covers every aspect of it because what it does is basically have the entire validation process being done twice once in the kernel itself by CIDLL and then it holds a copy of the policy in the secure area that the kernel can touch and it basically does the entire validation there and only then it provides the execution permission so without that validation nothing will work and that's it you can check out our blog for additional data and we're done thank you


Remember that the MHC, the major histocompatibility complex, MHC, is basically a protein platform that provides information about what's going on inside a cell. And I want you to take a second to visualize this. All cells have MHC1 platforms except not red blood cells. Did you hear that? That's actually whoa. That's the reason why you can do blood transplants, blood transfusions, between they're easy. I can donate my blood and 40% of the United Statesian population can accept my transplant. That's unbelievable. Not 40% of the population could accept a heart from me or a kidney from me or an eyeball or skin from me, a much smaller percentage. And it's because of these MHC1 platforms. That actually, you have to match MHC1 platforms that I want to trade body parts with someone. Because my immune system goes, dude, that's my MHC1 platform. All my cells have it except for my red blood cells. If somebody else's MHC1 comes in, I know that that's not me and I will attack it and kill it. So MHC1, remember, it's, let's just say we ate, we have some little, here's the little virus. And it's inside our body. We're doing our thing. Let's just go ahead and throw that virus into a vesicle. We find it. We're like, let's digest this thing. I don't know what this is in here, but it's what's happening inside me. So I feel like giving a big woof woof to the world and letting them know what's happening with me.  And then the little pieces of virus, after it gets broken up by the vesicle that's digesting it, those pieces of virus are sent to the endoplasmic reticulum. So they go to the endoplasmic reticulum. Now think, what happens in the endoplasmic reticulum? What is the endoplasmic reticulum? Remember, this is where proteins are processed. Proteins that are built in ribosomes can be folded and made into their proper shapes in the endoplasmic reticulum. So guess what happens with these virus parts? The endoplasmic reticulum says, I got you, dog. Let me take that virus part that you have. And I have a little MHC platform right here. And I'm building it as we speak, so I'm just going to add that little virus part to this platform inside the endoplasmic reticulum. Does anybody remember? I wish you were here so that you could holler out. Hala, hala. So maybe remember what happens next. Remember how the endoplasmic reticulum like pinches off and sends a little vesicle to the Golgi body? That was that little stack of pancakes. And so the Golgi apparatus is going to be like, I got this fantastic little bubble of MHC. Now look at what happens. The MHC is actually embedded in, I changed my mind about how I want to draw that, it in its own little vesicle that goes to the Golgi into another little vesicle and guess what happens to it. I'm just going to leave it in this vesicle. This isn't going to work for how I did it. I had to do it the first way.  I'm going to go like this. I don't even think I need to send it to the Golgi apparatus. And now I think this is going to work. Watch. I'm going to take it up here and I'm going to exocytose this. I know that I cannot draw this well.  And it had the little piece of virus attached to it and now what's on the surface of my cell? My platform, my MHC1 platform is on the surface of my cell and it has that little virus piece in it. Okay, you got it? Somebody's going to come checking that to say, now natural killers we know will come and check that and they can identify general problems. But the acquired immune response, your B cells and your T cells, actually your T cells are going to come along and they're going to be able to read this and know, uh-oh, I think there's a virus in there and they're going to do their thing. Everybody except red blood cells have these platforms to let you know what's going on inside. Now MHC2, not everybody has MHC2 and MHC2 is required to activate our acquired immune response.


who would be like a sleeper team in the playoffs, who's gonna make some noise. That's not there yet, but might do some damage to some teams. My sleeper probably would be the Miami Dolphins. The Bills, I mean, they're up and down. I can't be here. That'd be like a bad seventh seed to play. I wouldn't want to be like number two playing the Bills. Depends on the day. You don't know what Bills teams you're gonna get right now. And obviously Josh Allen, I mean, he's a good quarterback, but there's a lot of evidence flow with this game. So like I said, just never know with that team.


Hybrid and endovascular operations are increasingly used as alternatives for traditional surgery in the treatment of patients with chronic ischemia of the lower limbs. Research has shown that these procedures can reduce the risk of cardiovascular events and infection, and in many cases, limb salvage is possible. However, the effectiveness of each procedure depends on the severity of the patient's condition, the location of the blockage, and the skill of the surgeon. This article was authored by K. H. S. Makhamadeva, A. D. Gebov, A. K. Beratov, and others.


G'day, how are you going? Welcome to Brutalosophy and if you're new here, my name is Tech and as I work and live on Wajik Country in Western Australia, I acknowledge the Wajik people of Nungabuja. Today, I'm taking a look at this very laid-back work boot, the Red Wing 3139 Work Chaka. This is the Red Wing Work Chaka Boot. The model number is 3139 which indicates it as the Work Chaka Boot in the Copper Worksmith Leather Makeup. It's 105mm tall or a little over four inches. I don't have a lot of chaka boots so this is a slight variation in my collection which is focused more on six inch or above boots. As a chaka, basically an ankle length boot, it has only three islands and is built around what is quite a slim last for Red Wing boots which are more focused on round and bulky toed work boots like the Iron Ranger or the Blacksmith or the wider Rumi Alasip Mok Toe boots. You can see the slimness of the design from the top and from the side. The toe box is also sleek and has a low volume. The stitching pattern, especially along the quarters and on top of the vamp, add a very attractive interest starting with the famous Red Wing Puritan triple stitch on the quarters and this interesting vamp piece that sets apart from the quarter and making the stylish joint to the tongue. It's set on a slim wage sole so the whole appearance is almost dressy. As I said the boot style is a chaka and the most famous example of a chaka is of course the Clark's Desert Boot. As far as categories go, a desert boot is always a chaka but not all chakas are desert boots. The chaka boot design goes back to the kingly sport of polo in India. In polo a chaka is a playing period of about seven minutes. You have between four to six chakas per game. They weren't actually worn in the game when players wore riding boots or jog per boots. I know the chaka boots were usually worn after the game when the players met up in the club bar to enjoy gin and tonic after the match. Particularly in India chakas were made of softer suede or calf skin and provided sole feet with comfort after the game. The Clark's Desert Boot is a specific type of chaka boot designed by the Clark family after they saw how the Indian and South African officers in the desert war of the 1940s wore these very comfortable boots instead of the British Army's stiff service ammo boots. The desert boot was put on top of a crepe rubber sole for comfort and for stealth and was originally made only off suede for the comfort in the heat and was of a stitch down construction to keep the sand out. A chaka as a wider category class includes desert boots but also includes ankle boots with a low number of eyelets made up of any material and can be on a different type of heeled or flat sole. So that being said chaka boots tend to be on the casual side but there are makers such as Ellen Edmonds, Carmina, Crocodon Jones and Loak who make chakas in dressy smooth leathers that can even be worn with a suit. In this case these can't be worn with a suit. Some might try but certainly they can be worn as business casual. They work with simple dark pants and a business casual top such as a button down with or without any layers. They'll work with any kind of chinos and because of their coppery red color can match colors ranging from earth tones like brown to other neutral colors like black or navy. Since redwing labeled them as work boots obviously they'll also go with jeans and your rugged casual kind of gear. The redwing name work chaka puzzles me a little bit. Now work as it relates to boots can be a contentious subject from the um hey dude you don't work so you can't wear a boot for eternity. The term work heavily signifies manual labor. Most others would retort. I work too buddy. I work at a desk or in a hospital or I drive for a living or whatever. Anyway redwing however being predominantly a work boot as in manual work work boot company when they name this a work chaka I have to assume they mean that you can wear this for manual labor. If so I'm saying it's a pretty restricted kind of manual labor. Being a short boot it's not particularly protective or supportive although the leather is thick and I'll go more into that later but being so sleek lasted it's not exactly comfortable when you're kicking things around at work. I can't see a concrete worker or a steel worker wearing these in place of their technical work boots. I can't see tradies wearing these in in place of their blunt stones for example or their redwing mock toes. According to their website the work chaka line were made for indoor work so what we're talking about office workers or people like finishing carpenters and cabinet makers. So let's take a look at the maker redwing shoes. If you haven't heard of redwing you're either new to the world of boots or you're a newborn child. Redwing loom large in the field of boots and are themselves an enormous company. They are amongst the top 50 largest companies in their home US state of Minnesota. Some estimates of their revenue have them earning nearly 600 million US dollars a year in sales. So a big company. They were founded by Charles Beckman in 1905 and are still based in the town of Redwing Minnesota and that town having a population of under 20,000 I assume it's a bit of a company town. In the late 1980s they bought an old tannery founded in 1872 called SB Foot Tanning. This allowed them full vertical integration in their operations from design to manufacture to retail. Redwing make a huge range of footwear not only as Redwing but also under different brand names like Works and Irish Setter. The Redwing brand is now split between their workwear category and their heritage boots. Some of the products are now made outside the US primarily in Asian countries but their heritage lines are still made in Minnesota in Missouri and Kentucky. Of course their most famous heritage boots are the Iron Ranger and the 6 inch mock toe boot. Now let's move on and look at how these are put together. As usual I'll start from the bottom and I'll work my way up. Under it all is a Redwing proprietary wedge sole they call the Atlas Tread sole. It's a polyurethane plated sole which is a polymer compound really not a rubber. That polyurethane layer is made on top of a blown rubber layer in the wedge so it gives you durability because of the toughness of the polyurethane along with comfort because of the bounciness of that blown rubber. The sole pattern is an interesting one. I've never seen anything like it before. It does provide good grip under most conditions including wet ones but the deep treads do tend to get dirty even if you don't pick up stones and gravel. The sole is attached to the uppers using a 360 degree Goodyear welt construction. The advantage of a Goodyear welt is that it's water resistant and it can be easily re-sold. I've done a video on Goodyear welting if you want to see it. I'll leave a clickable link up there. Basically it's a strip of leather called the welt and it's affixed all the way around the boot. It's sewn on the inside edge to the turned-in uppers of the boot while the outside edge of that welt is then sewn to the midsole. Often it's also sewn through to the outsole but as in most wedge soles that's not what happens here. The welt is sewn to a rubber midsole and then the wedge outsole is glued onto the midsole. Some people freak out when they don't see a stitch under the boot or they freak out if they see a stitch but it's not set inside a channel to protect that stitch. They think the outsole will fall off. Actually the stitch going through the outsole is only a reinforcement. Usually the glues that bootmakers and cobblers use if applied, activated and attached properly is strong enough to hold on any outsole. Inside the boot is a cork filler that fills the cavity caused by the 4mm thick welt going around the outside edge of the boot. The cork filler gives long-term comfort as a foot bed. Embedded in the cork filling is a steel shank to give the arch of the boot some stability. Although I have to say that I'm never really sure why a wedge sole boot with no gap between the heel and the ball of the foot needs extra arch stability. Further on inside the boot is a thick leather insole. This is glued on top of the cork filling and steel shank. You can see it when you look inside the boot. I'm not sure the camera can pick this up. I can't measure the thickness of it but from sight I'd say it's also a very hefty 4mm of veg tan goodness. The thick leather insole is also an aid to long-term comfort as it will mold to the shape of your foot with long enough wear. So moving on up, the uppers are made from SBFoot's oil-tanned leather in a color that they call copperworksmith. That's a good description. The color is very reminiscent of a deep burnish copper with some undertones of purplish gray in certain light which is why I've substituted the usual tazlon laces that come with the boot with these blue-gray laces which I think really bring up that deep copper color. As I've said, Redwing own SBFoot and they've been around for 150 years anyway so you can say that they know how to tan leather. While oil tanning is a centuries-old method of tanning leather in mostly fish oils, today it's really a way of finishing the leather in the tanning process.  What's produced, in this case at least, is a 2mm thick leather that's supple and at the same time tough and hardy, especially where reinforced by the canvas lining in the vamp. The leather can feel stiff. Inside the boot, as I've just said, the vamp is lined with canvas but the shaft is unlined. The tongue is lined with the same leather backed up on itself, turned around so that the two rough outsides are stitched together. The tongue is ungusseted but it's short and it's two layers thick so there is no tendency to slip to one side or the other. The heel counter is internal, it's not very thick and I don't know for sure but the flexibility makes me think that it's leather rather than some sort of plastic. On the inside, again I'm not sure the camera will pick it up, it's covered by a suede heel counter cover. The suede's supposed to grip your sock and prevent heel slip. On the outside the stitching is even and clean, there's the famous Puritan triple stitch with a single contrasting stitch. The Puritan stitching machine, which was first patented in 1893, actually stitches all three stitches at the same time and Redwing have their own full-time staff to repair and maintain their machines. The pattern is really attractive with this little gap between the quarter pieces and the vamp piece, quite unusual. There are three simple nickel eyelets and the edges of the facings and the collar are all nicely rolled. It's not too hard to take care of this leather, it's an oil-infused leather so should keep itself reasonably hydrated unless you take it for a swim or through equally harsh conditions. As always the key is to keep it clean. Give it a good brushing with a good horse hair brush after every I'd say three or four wears and if it picks up sand and dirt give it a wipe with a damp cloth to remove the worst of the dirt. If you do use this as a work boot I would clean it every day and I would try and leave it for a day or two before you pick it up again. If it really gets dirty you can saddle soap these boots. I have conditioned this pair once with a little smear of Neitzfoot oil. It didn't darken the leather at all and to my touch has replaced the oily field of the leather without making the surface tacky or oily. You can I think also safely condition it with Venetian shoe cream that's my go-to conditioner for pretty much all of my smooth leather boots or I'm sure you can also use a big four. Check out the description below for some links to where you can get these conditioners and other care stuff. Now to sizing and fit. If you subscribe to my channel and if not why not you should click on subscribe now. If you've been following my other videos you know that I'm true to size on a US Brannock device at 8.5 D width. That equates to a UK or Aussie size 7.5 in a regular or average width. However in my Heritage Star boots I usually wear an 8D because for some reason boot companies make boots larger than they really are. So I wear an 8D in my iron ranges in the roomie number eight last and also an 8D in my 875 mock toes in the even roomier number 23 last. This is Red Wings 210 last. A last is the foot shape mold that the boot maker stretches the leather over to create the shape of the foot. So obviously apart from being foot shaped the last is also shaped in the shape of the design of that particular boot. The 210 last is a slim last as you can see. It's a definite almond shape of the toe and sneaks in quite a lot from the ball of the foot into the toes. This is an 8D as well and I have to say that while it fits it is snug. The length is right I have easily a thumbs width ahead of my toe to the end of the boot. The width at the ball of the foot is fine. The knuckles of my toes don't feel particularly squeezed where I do feel the snugness is in the toes especially my little toes where the last starts to curve into the tip. They don't hurt but I suspect once they really break in they'll be fine. But at the moment I feel like I really need to rub my toes in the evening when I take these off. Do you know the feeling? These are not fully broken in yet so the sole is stiff still the leather is stiff and not yet warmed up by the heat of my feet over time. The insoles still feel stiff. They're vegetarian leather and I've not made any impression on them. I have a lot of boots and chuckers are not my favorites so I don't wear these often enough so they haven't really broken in. They're not my most comfortable boots so I tend not to wear them a lot it's a vicious circle. So guys I'm actually going to sell these. I'm going to put them up on eBay so check up my username there drive 788. I'll put them there in the next few days if I haven't already by the time I upload this video. Otherwise DM me and my Instagram account techo-t-e-i-k-o-h or one word. I'm going to ask I think Aussie $200 for them. I'll find out postage to you wherever you are and I'll let you know if you contact me. So on to cost and value. In the US they sell for US $280. You can buy them in Australia from time to time they're not always available for around 420 to 500 Aussie bucks. You can get iron rangers here for just over 560. The classic 875 mockto for about $550. I wouldn't even begin to compare them with Clark's Desert boots which you can get for under $200. There's just no comparison between the quality of the make or of the materials. A closer comparison might be made with Doc Martens who also have Chuckers that they sell for between $200 and $300. But even then be aware that those are not Goodyear weltered but they rely on DM's heat welting which is not as easily resoldable. So all in all it's probably a bit more expensive than other Chucker boots you can get but honestly a level above in terms of construction, in terms of quality and in terms of the materials. As I've said Chuckers are not my favorites but if I were looking for a tough casual Chucker would I buy these? Yeah I would at that price. So there you have it guys and gals. On the one hand it's a tough well-made boot and with Redwing's brand reputation it's pretty much a winner. On the other hand is it too tough for casual wear? I haven't really been able to break them in with my casual wear. I don't know I've laid it out for you so you be the judge. I hope you like this review if you have you know the drill click on the like button to help me grow my channel and therefore allow me to bring you more reviews. And if you haven't already click on subscribe so you get to be notified when I upload more boot reviews when I upload more deep dives into brands and I make videos about comparisons and long-term wear reports. Until then take care and I'll see you again soon.


Hi everybody, Joe for Jasper's Case Breaks dot com coming at you with 2021 Mosaic Baseball Hobby Pack Break number 11 with eight of those dual case spots, those double header break spots for Chrome Black being given away. So two different dice rolls. First one will be for the pack break, second one will be for the giveaway. Big thanks to everybody here for rallying around this break, for making it happen. And all the teams are in. Let's roll it and randomize it one and a three, four times for names and teams. One, two, three, and a one, fourth and final time. One and a three, four times for the teams, one, two, three, and a one, fourth and final time. All right, here's the first half of the list right here and here's the second half of the list right over there. Sort alphabetically by team and let's just print this baby out, let's rip this pack up and see who's going to win spots in that dual case break, which is right here. If you're watching live, all we got to do is move like four spots straight up and then we're in breaksville. Who do I have in the college football championship game? Who's in the football college football championship game? I don't fall to college closely enough. Do they have that the playoff set? I'll say Alabama. I feel like that's always a always a safe bet, right? Here's Cabrine Hayes rookie card and mosaic. That's going to be for Kevin in the Pirates. It's not bad, rookie card, some other inserts here as well. All right, once again, big thanks everybody who got into the action here. Now we're going to randomize all of your names again and see who's going to win those dual case spots. So new dice roll. Let's roll it and randomize that list three and a one four times top eight after four. Good luck. One, two, three and four. So from nine on down, it's only the top eight from nine on down. Sorry, Ryan. Sorry, everybody. Sad times, but much happier times for the top eight. You're in the next break, Josh, Ryan, Josh, Josh, Josh, Josh, Danny and Ryan again. Like I said, I don't feel so bad for Ryan just missing out because you ended up getting a couple spots anyway. So there you go. Top eight. Congrats. Thank you. We'll see you in the next video for the next one. Bye-bye.