Pushkar-Bhuse

Results 9 issues of Pushkar-Bhuse

This PR fixes #874 ### Description of changes This PR attempts to transform how data is stored in the `DataStore` entry. The main idea behind this new format is that...

data_efficiency

This PR fixes #840 . ### Description of changes This PR mainly includes fine-tuning CV ontologies to be used correctly with the `DataStore` setup. Once this was completed, we included...

**Is your feature request related to a problem? Please describe.** The current structure of entries stored in Data Stores is not scalable. This was made apparent by the requirement of...

data_efficiency

**Describe the bug** During augmentation, the newly created data pack copies the links and groups of the original data pack. We suspect that the user defined features which may be...

bug
data_aug
e/3

**Is your feature request related to a problem? Please describe.** Currently, there are two ways to create augmentation techniques, as `Ops` or as `Processor`'s. This causes inconsistency in for new...

This PR adds a functionality mentioned in the [comments](https://github.com/asyml/forte/pull/900#discussion_r959740247) of #900. ### Description of changes In this PR, we modify the interface of `FList` to store and process `MultiPack` entries....

This PR is the first step towards fixing #881 ### Description of changes Current, when fetching entries from a `DataPack` or `MultiPack` using the `get` method, Forte converts data store...

**Is your feature request related to a problem? Please describe.** Currently, the `in_span` and `in_audio_span` methods only handle entries of type `Union[int, Entry]`. We want to allow these methods to...

data_efficiency

**Is your feature request related to a problem? Please describe.** The resources used to define the test cases in `data_store_test.py` and `data_store_serialization_test.py` are the same in many cases. For example:...

data_efficiency