Upstream Advanced
Luisa Rodocker
At Lilly, we unite caring with discovery to make life better for people around the world. We are a global healthcare leader headquartered in Indianapolis, Indiana. Our employees around the world work to discover and bring life-changing medicines to those who need them, improve the understanding and management of disease, and give back to our communities through philanthropy and volunteerism. We give our best effort to our work, and we put people first. We\u2019re looking for people who are determined to make life better for people around the world.
Lilly is currently constructing a cutting edge facility for the manufacture of new modalities including Gene Therapy. At Lebanon, Indiana, this facility will be Lilly\u2019s most technically advanced manufacturing site focused on the delivery of the next wave of innovative products at Lilly. It will include next-generation manufacturing technologies and advanced data collection and analysis platforms that will deliver improvements in safety and quality, and process performance. This is a unique opportunity to be a part of the team for the startup of a greenfield manufacturing site, and the successful candidate will help to design, commission and start up the facility for both clinical and commercial supply.\u202F
This is an exciting opportunity to help build a state-of-the-art facility and Quality System from the ground up.\u00A0The TS/MS team will own all areas of technology transfer, process validation, and process stewardship.
Upstream Bioprocess\u00A0\u2013 Technical Services/Manufacturing Scientist (TS/MS) role is responsible for providing technical support for the development, implementation, and technical transfer of compliant manufacturing of gene therapy drug substance and drug product for clinical and commercial manufacture. The successful candidate will be required to build deep technical expertise in their area of responsibility (including in-depth knowledge of the science behind the molecule and the process), have strong working skills on the manufacturing equipment set and control systems, and consistently demonstrate strong data-driven decision-making and problem-solving capabilities. They may also work to ensure that the process is in-control, capable, compliant, and maintained in a validated state through continual monitoring and may play a role in by implementing new technologies and process improvements in the manufacturing environment.
I have local master and develop branches. I do all my work on develop and then merge them into master for releases. There is a remote branch, upstream/master which has changes I want, but I want to rebase my changes in develop (which shares a common ancestor) on top of its changes and put them back into develop. I've already done git fetch upstream.
UPDATE: So I looked at @torek suggested git rebase --onto command, like How to git rebase a branch with the onto command?, and all their refed docs, and think my problem is still one or two levels up than what I've read (because there are two repos and 5 branches involved). Here is the summary:
A = 2f5eaaf add file-a; B = 85afa56 update file-a; and so on. I picked the later ones to be the "primes" based on subject lines, although that might be backwards: perhaps the one labeled B should be B' for instance. It seems likely that despite the same subject line for commits B and E, they have different patch-IDs (do different things to file-a), and it's hard to say whether matching up the two "more updates" commits here (calling the second one on the bottom row C') was right.
Moving one branch name is insufficient. It's not particularly harmful and we could allow Git to do it, but let's just do this directly with cherry-pick. We'll start by checking out the commit onto which everything should land, creating a new branch name:
(again the two names used here are just ways of typing in the raw commit hash IDs without having to type in raw commit hash IDs). The two-dot syntax here means any commits reachable from the second specifier, excluding all commits reachable from the first specifier, so this means commits from J all the way back to the root, minus commits from D all the way back to the root which means E-F-G-H-I-J.
Now that we have the commits we want, we merely need to place the particular labels. Since one or more of these labels will point to commit G', it helps to redraw the above with H'-I'-J' on a row of its own:
To move upstream's dev/br1 and cause our upstream/dev/br1 to move, we now need to git push --force-with-lease or similar to upstream, which also assumes that we have permission (on whatever system hosts upstream: Git itself doesn't "do" permissions, but sites like GitHub and others do, for obvious reasons). The --force-with-lease tells our Git to verify that their dev/br1 still points where we expect; if we're sure that this will be the case, we can use plain --force. Either way the command is, or resembles:
The key here is to understand that the names are largely irrelevant. All that actually matters are the commits, which are identified by their hash IDs. The trick is that we find the commits using the names, so that makes the names relevant.
With the (local) repository's names now pointing to the copies, it's once again just a matter of using git push --force-with-lease or git push --force to get the other Git software, working with the two other repositories, to update their branch names, so that our own Git's memories in our remote-tracking names get updated.
(If you can't literally force-push to upstream or origin, you can still send the updated commits, e.g., via pull requests, but someone else will have to convince the other repositories to actually move their branch names to take in the new commits.)
This project outlines the benefits and operational challenges of blending advanced treated water with raw water or filtered water at SWTPs, developed strategies for optimizing SWTP unit processes to address challenges, and developed approaches for validating pathogen log reduction credits under a direct potable reuse regulatory framework. Research partner: California State Water Resources Control Board. Published in 2023.
This research developed and validated novel surrogates for awarding virus log reduction values (LRVs) in membrane-based potable reuse systems. Specifically, the project involves three research themes: (1) development...
Reverse osmosis (RO) and nanofiltration (NF) membranes provide high levels of treatment for microbial and chemical pollutants alike. They play key roles in desalination, potable reuse projects, and...
c80f0f1006