bonito VS llvm-project

There is a technology called Nanopore. I’ve never used it myself but the concept was to be able to sequence samples of nucleic acid out in the field. A quick pubmed search indicated that it can detect miRNA, but maybe with some modifications. https://nanoporetech.com Best of luck with it!

> An unpopular opinion: there are too many other logos that look like the original logo

There are also too many logos that look like the new logo. The first blue circle logos that spring to mind are Blue Circle Cement/Tarmac/Lafarge [1] and Oxford Nanopore [2].

[1]: https://en.wikipedia.org/wiki/Tarmac_(company)

[2]: https://nanoporetech.com/

Oxford Nanopore Technologies (https://nanoporetech.com/) | Front end developer | Full-time | Oxford | Remote (UK)

Oxford Nanopore Technologies is headquartered at the Oxford Science Park outside Oxford, UK, with satellite offices and commercial presence in many global locations across the US, APAC and Europe. Our DNA/RNA sequencing platform is the only technology that offers real-time analysis (for rapid insights), in fully scalable formats from pocket to population scale. Our goal is to enable the analysis of any living thing, by anyone, anywhere.

Tech stack: Electron, Stencil, React, Typescript, RxJS, GRPC

For more details, please email: [email protected]

Ok this isn't really my area but I know that there are labs/companies performing these types of electrical current disturbance measurements of membrane-type proteins for both DNA sequencing (https://nanoporetech.com/) and protein sequencing (https://www.nature.com/articles/s41587-019-0401-y).

Now nanopore sequencing is solid state and gets much longer reads. https://nanoporetech.com/ and https://en.wikipedia.org/wiki/Nanopore_sequencing

Also best of luck with the basecaller, I will say that the latest guppy versions are very good, both in terms of accuracy and speed, as they are GPU accelerated and the best I've seen in accuracy. You may also be interested in Bonito, a tool to generate your own GPU basecalling model or tweak existing models to your data. https://github.com/nanoporetech/bonito.

'Computer Architeture: A Quantitative Apporach" and/or more specific design types (mips, arm, etc) can be found under the Morgan Kaufmann Series in Computer Architeture and Design.

"Getting Started with LLVM Core Libraries: Get to Grips With Llvm Essentials and Use the Core Libraries to Build Advanced Tools "

"The Architecture of Open Source Applications (Volume 1) : LLVM" https://aosabook.org/en/v1/llvm.html

"Tourist Guide to LLVM source code" : https://blog.regehr.org/archives/1453

llvm home page : https://llvm.org/

llvm tutorial : https://llvm.org/docs/tutorial/

llvm reference : https://llvm.org/docs/LangRef.html

learn by examples : C source code to 'llvm' bitcode : https://stackoverflow.com/questions/9148890/how-to-make-clan...

See

https://github.com/llvm/llvm-project/issues/88344

https://fortran-lang.discourse.group/t/flang-new-how-to-forc...

You can never mistake type_declaration with an identifier, otherwise the program will not work. Aside from that constraint, you are free to name them whatever you like, there is no one standard, and each parser has it own naming conventions, unless you are planning to use something like LLVM. If you are interested, you can see examples of naming in different language parsers in the AST Explorer.

> There is one way to make the LLVM JIT compiler more usable, but I fear it’s going to take years to be implemented: being able to cache and reuse compiled queries.

Actually, it's implemented in LLVM for years :) https://github.com/llvm/llvm-project/commit/a98546ebcd2a692e...

> It's true, this was a CVE in Rust and not a CVE in C++, but only because C++ doesn't regard the issue as a problem at all. The problem definitely exists in C++, but it's not acknowledged as a problem, let alone fixed.

Can you find a link that substantiates your claim? You're throwing out some heavy accusations here that don't seem to match reality at all.

Case in point, this was fixed in both major C++ libraries:

https://github.com/gcc-mirror/gcc/commit/ebf6175464768983a2d...

https://github.com/llvm/llvm-project/commit/4f67a909902d8ab9...

So what C++ community refused to regard this as an issue and refused to fix it? Where is your supporting evidence for your claims?

For everyone else looking for the magic in this almost 7k lines monster, look at line 6610 [1].

[1] https://github.com/llvm/llvm-project/blob/8ec28af8eaff5acd0d...

Through value tracking. It's actually LLVM that does this, GCC probably does it as well, so in theory explicit bounds checks in regular C code would also be removed by the compiler.

How it works exactly I don't know, and apparently it's so complex that it requires over 9000 lines of C++ to express:

https://github.com/llvm/llvm-project/blob/main/llvm/lib/Anal...

https://github.com/llvm/llvm-project/blob/main/flang/docs/F2...