Contact Our Lab for Collaborations, Visits and Inquiries

Welcome to Our Research Lab

We welcome clear, practical inquiries from researchers, prospective doctoral students, engineers, and organizations interested in computational design research.

Most conversations with the lab begin with a focused question: a possible collaboration, a research visit, a PhD supervision inquiry, or a request to discuss methods used in topology optimization, generative design, multi-objective optimization, or engineering applications. A short message with the right context is usually enough to decide the next step.

For general academic contact, please write directly to the lab director. We do not use a public contact form on this page, and we do not list phone numbers or physical addresses here. That keeps communication traceable and reduces the risk of missed technical details.

Direct Contact Information

Attachments can be useful, but they should not carry the whole inquiry. In the email body, summarize the question, the proposed work, and what you are asking from the lab. For example, “feedback on a topology optimization formulation for a lightweight bracket” is much more useful than “possible collaboration in optimization.”

Prospective Researchers and PhD Students

Prospective PhD students and visiting researchers should write with enough detail to show how their interests connect to the lab’s technical work. A polished biography is less important than a precise research question.

Helpful messages usually include a brief academic background, the methods you have already used, and the kind of problem you want to work on. If you have experience with simulation, optimization, CAD workflows, numerical methods, scientific computing, or experimental validation, describe one project in plain terms. What was the problem? What did you implement? What did you learn from the result?

Funding, admission routes, supervision capacity, and institutional requirements vary by program and timing. Because those constraints change, an inquiry should not assume that an opening exists. The strongest first message makes the research fit visible and leaves room to discuss formal eligibility later.

Partnership and Collaboration Opportunities

Collaboration inquiries work best when they name both the technical problem and the decision that depends on it. In applied research, the hard part is rarely just running an optimizer; it is defining constraints, interpreting trade-offs, and deciding which result can survive engineering review.

For academic collaborators, a useful starting point is a compact description of the research gap, the methods under consideration, and the expected form of contribution. For industry or engineering teams, it helps to describe the component, system, material, design constraints, and evaluation criteria. Confidential details should stay out of the first email unless a formal agreement is already in place.

Some collaborations begin with a manuscript idea. Others begin with a stubborn implementation issue: a mesh that behaves poorly, a design space that is too restrictive, or an objective function that hides the real engineering priority. Both routes can be productive, but they need different preparation. A manuscript conversation should include the intended contribution. An implementation conversation should include the current workflow and the point where it stops being reliable.

The trade-off is simple: the more specific the initial description, the easier it is to judge feasibility; the more sensitive the project, the more care is needed before technical material changes hands.

Lab Visitation Protocols

Visits should be arranged in advance by email. Please do not assume that an informal visit can be accommodated without prior scheduling, even when the purpose is academic. Lab time is often tied to supervision, writing, computational work, and project meetings.

A visit request should state who will attend, the reason for the visit, the preferred timing, and whether the meeting is intended as a research discussion, student inquiry, collaboration planning session, or technical demonstration. If a visit involves multiple people, identify one contact person who can coordinate details.

For data handling, website use, and general terms that may apply to digital communication with sciartsoft, see the Privacy Policy and Terms of Use.

The goal is not to make contact difficult. It is to make the first exchange useful enough that the next step is clear.