Get in touch.

Share a scientific dataset, ask about using a benchmark, or report a problem with an example. A link and a short description are enough to begin.

Contact the project lead

Xiongye Xiao
DUAL Lab · UTK EECS

[email protected]

Opens your email application. You choose what to include and send.

DUAL Lab’s public contact page

Discuss a source or idea

  1. Describe the resource and its possible scientific use. Include a public source link and one representative example.
  2. Mention the version, known reuse terms and preparation questions. A draft from the proposal form is optional.

Request review of a checked package

  • Exact version and an immutable download of the actual package, or a previously agreed transfer route.
  • Saved check report and usage card with loading instructions.
  • Complete file inventory, including supporting files and any missing materials.

The checker’s request draft includes the report and inventory you enter. Attach it to avoid writing them again; add the usage card and actual files or agreed access route yourself.

Email a review request

After you send it: a maintainer replies with a receipt ID, received version, review owner and next step. That acknowledgement starts the review process; your local draft ID is not a receipt. Reviewer assignments and timing are confirmed separately. Receipt and status template.

Report an example run

Include the example version, command, expected and observed results, and relevant output. Mention your Python version or environment if the example failed to run. Prepare reproduction notes.

For a correction, include the page address, the statement and supporting evidence.

Before sharing

Share public descriptions and links first. Keep restricted datasets, credentials and protected evaluation answers out of email; agree a permitted access route separately. Acceptance and publication require review and permission.

Your information and files

Forms and checks run on your device. Public downloads require no personal information. You choose what to share by email and whether to appear on the community map.

Local drafts and file checks

The feedback form keeps inputs in the current page only. The contribution form transfers a draft through session storage when you switch language in the same tab; the destination removes the transfer. Abandoned transfers expire after two minutes and are discarded on a later form visit. Downloaded drafts stay on your device. The checker reads selected files locally and does not upload them.

Email, attribution and the community map

Opening your email application does not send a message. Emailed feedback is private project correspondence; contact the project lead to correct or remove it. Public names, affiliations and city-level map locations require agreement and can be updated or withdrawn. Locations are never inferred from IP addresses; downloads do not add people to the map.

Hosting and external services

Fonts are hosted with the site. There are no analytics or advertising scripts. The hosting provider may keep ordinary request logs. External data hosts and email services have their own privacy practices.