repo stringclasses 43
values | docfile_name stringlengths 7 40 | doc_type stringclasses 11
values | intent stringlengths 8 128 | license stringclasses 3
values | path_to_docfile stringlengths 29 116 | relevant_code_files sequencelengths 0 12 | relevant_code_dir stringlengths 0 54 | target_text stringlengths 339 44.2k | relevant_code_context stringlengths 1.12k 23.2M |
|---|---|---|---|---|---|---|---|---|---|
ynput__OpenPype | assignments_and_allocations.rst | Tutorial / Subdoc | Working with assignments and allocations | MIT License | ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/doc/example/assignments_and_allocations.rst | [
"ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/source/ftrack_api/session.py"
] | Working with assignments and allocations
The API exposes assignments and allocations relationships on objects in
the project hierarchy. You can use these to retrieve the allocated or
assigned resources, which can be either groups or users.
Allocations can be used to allocate users or groups to a project team,
while a... | # :coding: utf-8
# :copyright: Copyright (c) 2014 ftrack
from __future__ import absolute_import
import json
import logging
import collections
import datetime
import os
import getpass
import functools
import itertools
import distutils.version
import hashlib
import appdirs
import threading
import atexit
import request... | |
ynput__OpenPype | custom_attribute.rst | Tutorial / Subdoc | Using custom attributes | MIT License | ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/doc/example/custom_attribute.rst | [
"ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/source/ftrack_api/session.py"
] | Using custom attributes
Custom attributes can be written and read from entities using the
custom_attributes property.
The custom_attributes property provides a similar interface to a
dictionary.
Keys can be printed using the keys method:
>>> task['custom_attributes'].keys()
[u'my_text_field']
or access key... | # :coding: utf-8
# :copyright: Copyright (c) 2014 ftrack
from __future__ import absolute_import
import json
import logging
import collections
import datetime
import os
import getpass
import functools
import itertools
import distutils.version
import hashlib
import appdirs
import threading
import atexit
import request... | |
ynput__OpenPype | encode_media.rst | Tutorial / Subdoc | Encoding media | MIT License | "ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/doc/example/encode_media.r(...TRUNCATED) | ["ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/source/ftrack_api/session(...TRUNCATED) | "Encoding media\n\nMedia such as images and video can be encoded by the ftrack server to\nallow play(...TRUNCATED) | "# :coding: utf-8\n# :copyright: Copyright (c) 2014 ftrack\n\nfrom __future__ import absolute_import(...TRUNCATED) | |
ynput__OpenPype | web_review.rst | Tutorial / Subdoc | Publishing for web review | MIT License | "ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/doc/example/web_review.rst(...TRUNCATED) | ["ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/source/ftrack_api/session(...TRUNCATED) | "Publishing for web review\n\nFollow the example/encode_media example if you want to upload and enco(...TRUNCATED) | "# :coding: utf-8\n# :copyright: Copyright (c) 2014 ftrack\n\nfrom __future__ import absolute_import(...TRUNCATED) | |
ynput__OpenPype | sync_ldap_users.rst | Tutorial / Subdoc | Sync users with LDAP | MIT License | "ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/doc/example/sync_ldap_user(...TRUNCATED) | ["ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/source/ftrack_api/session(...TRUNCATED) | "Sync users with LDAP\n\nIf ftrack is configured to connect to LDAP you may trigger a\nsynchronizati(...TRUNCATED) | "# :coding: utf-8\n# :copyright: Copyright (c) 2014 ftrack\n\nfrom __future__ import absolute_import(...TRUNCATED) | |
ynput__OpenPype | publishing.rst | Tutorial / Subdoc | Publishing versions | MIT License | "ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/doc/example/publishing.rst(...TRUNCATED) | ["ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/source/ftrack_api/session(...TRUNCATED) | "Publishing versions\n\nTo know more about publishing and the concepts around publishing, read\nthe (...TRUNCATED) | "# :coding: utf-8\n# :copyright: Copyright (c) 2014 ftrack\n\nfrom __future__ import absolute_import(...TRUNCATED) | |
ynput__OpenPype | security_roles.rst | Tutorial / Subdoc | Working with user security roles | MIT License | "ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/doc/example/security_roles(...TRUNCATED) | ["ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/source/ftrack_api/session(...TRUNCATED) | "Working with user security roles\n\nThe API exposes SecurityRole and UserSecurityRole that can be u(...TRUNCATED) | "# :coding: utf-8\n# :copyright: Copyright (c) 2014 ftrack\n\nfrom __future__ import absolute_import(...TRUNCATED) | |
ynput__OpenPype | list.rst | Tutorial / Subdoc | Using lists | MIT License | ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/doc/example/list.rst | ["ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/source/ftrack_api/session(...TRUNCATED) | "Using lists\n\nLists can be used to create a collection of asset versions or objects\nsuch as tasks(...TRUNCATED) | "# :coding: utf-8\n# :copyright: Copyright (c) 2014 ftrack\n\nfrom __future__ import absolute_import(...TRUNCATED) | |
ynput__OpenPype | review_session.rst | Tutorial / Subdoc | Using review sessions | MIT License | "ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/doc/example/review_session(...TRUNCATED) | ["ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/source/ftrack_api/session(...TRUNCATED) | "Using review sessions\n\nClient review sessions can either be queried manually or by using a\nproje(...TRUNCATED) | "# :coding: utf-8\n# :copyright: Copyright (c) 2014 ftrack\n\nfrom __future__ import absolute_import(...TRUNCATED) | |
ynput__OpenPype | timer.rst | Tutorial / Subdoc | Using timers | MIT License | ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/doc/example/timer.rst | ["ynput__OpenPype/openpype/modules/ftrack/python2_vendor/ftrack-python-api/source/ftrack_api/session(...TRUNCATED) | "Using timers\n\nTimers can be used to track how much time has been spend working on\nsomething.\n\n(...TRUNCATED) | "# :coding: utf-8\n# :copyright: Copyright (c) 2014 ftrack\n\nfrom __future__ import absolute_import(...TRUNCATED) |
ποΈ Long Code Arena (Module summarization)
This is the benchmark for Module summarization task as part of the ποΈ Long Code Arena benchmark. The current version includes 216 manually curated text files describing different documentation of open-source permissive Python projects. The model is required to generate such description, given the relevant context code and the intent behind the documentation. All the repositories are published under permissive licenses (MIT, Apache-2.0, BSD-3-Clause, and BSD-2-Clause). The datapoints can be removed upon request.
How-to
Load the data via load_dataset:
```
from datasets import load_dataset
dataset = load_dataset("JetBrains-Research/lca-module-summarization")
```
Datapoint Structure
Each example has the following fields:
| Field | Description |
|---|---|
repo |
Name of the repository |
target_text |
Text of the target documentation file |
docfile_name |
Name of the file with target documentation |
intent |
One sentence description of what is expected in the documentation |
license |
License of the target repository |
relevant_code_files |
Paths to relevant code files (files that are mentioned in target documentation) |
relevant_code_dir |
Paths to relevant code directories (directories that are mentioned in target documentation) |
path_to_docfile |
Path to file with documentation (path to the documentation file in source repository) |
relevant_code_context |
Relevant code context collected from relevant code files and directories |
Note: you may collect and use your own relevant context. Our context may not be suitable. Zipped repositories can be found the repos directory.
Metric
To compare the predicted documentation and the ground truth documentation, we introduce the new metric based on LLM as an assessor. Our approach involves feeding the LLM with relevant code and two versions of documentation: the ground truth and the model-generated text. The LLM evaluates which documentation better explains and fits the code. To mitigate variance and potential ordering effects in model responses, we calculate the probability that the generated documentation is superior by averaging the results of two queries with the different order.
For more details about metric implementation, please refer to our GitHub repository.
Citing
@article{bogomolov2024long,
title={Long Code Arena: a Set of Benchmarks for Long-Context Code Models},
author={Bogomolov, Egor and Eliseeva, Aleksandra and Galimzyanov, Timur and Glukhov, Evgeniy and Shapkin, Anton and Tigina, Maria and Golubev, Yaroslav and Kovrigin, Alexander and van Deursen, Arie and Izadi, Maliheh and Bryksin, Timofey},
journal={arXiv preprint arXiv:2406.11612},
year={2024}
}
You can find the paper here.
- Downloads last month
- 510